Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

DOS internationalization support (Developers)

posted by mbbrutman Homepage, Washington, USA, 25.11.2012, 20:05

> Correct, unless you go to a framebuffer textmode solution and forgo the
> hardware textmode, as many *nixes do.
Graphics would solve other problems (underlining, bold, etc.) that I can not handle using the text modes. But the text modes have the advantage of being the same across all of the adapters - MDA to VGA. And text modes are fast enough for the most primitive machines. (The 8088s are still very important to me.)


> libiconv is the standard answer, but if you can only display 256 chars, you
> don't need that much library support. (since even if you render certain
> accented characters to their non accented equivalent, there are still only
> 500 something mappings for a given codepage)
>
> We use such solutions to provide some minimal unicode awareness for little
> programs and programs involved in bootstrapping the system. The tables are
> postloadable, so new codepages can be added without recompiling the
> binaries.
>
> For fuller unicode support we usually try to tap in whatever system unicode
> library there is, to avoid
The support I need is basically just the mapping tables - given a Unicode character what is the correct character in the current codepage to use. (Or a close approximation.) (And the reverse is needed for keyboard input.)

Your approach for minimal Unicode awareness sounds similar to what I am thinking of. I want to make it more Unicode aware, not perfect. (I am never going to have the Asian character sets covered ...)

---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22760 Postings in 2121 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum