|
Post by zetathix on Nov 11, 2018 22:30:09 GMT 1
I am trying to find a solution for thai language which have problem with monospace in vDos, system consider upper or lower vowel letters as 1 letter and leave empty space over or under.
Do anyone know how to manage this problem? I am really hopeless now because I can't find solution which could get along well with vDos... There have solution in ntvdm before but I can't get same correct result with vDos.
Please help.
|
|
|
Post by Jos on Nov 12, 2018 9:34:53 GMT 1
Can you post screenshots to illustrate your problem (NTVDM and vDos)?
Jos
|
|
|
Post by zetathix on Nov 12, 2018 12:41:08 GMT 1
Thank you for your attention. I am really appreciate. This is the screen from NTVDM on the upper image, and vDOS is down below. I put some paper about thai language alphabets development from research of Thai technology department down below too. The solution in the actual DOS era, is using the driver which specify for showing thai language on DOS, but all DOS's drivers are already outdated, cannot contact any programmer which related to any drivers, and they all make vDOS cannot uses .TTF font as vDos's intention. The driver I have, if run on vDOS, it will locked the screen size to actual 640x480 because it's font embeded inside the driver itself I guess, and display will forced to totally wrong with driver on vDOS. So I decided to ask about the problem here in the forum, without this problem, vDos is very fine. PDF ABOUT THAI ALPHABET STRUCTURE
|
|
|
Post by Jos on Nov 12, 2018 14:25:33 GMT 1
I’m afraid you’re out of luck with Thai and vDos.
As the paper explains (I only had a glance): “A Thai word is typically formed by the combination of one or more consonants, one vowel, one tone mark, and one or more final consonants to make one syllable.”. All possible combinations of consonants and the rest will never fit in the 128 byte extended ASCII table. So the Thai driver under NTVDM most likely replaced INT 10 (BIOS video functions): If it encountered a “tone mark”, it combined that with the previously displayed character and updated the graphical image. vDos basic VGA graphic support will be the issue for incorrectly displaying the Thai characters in graphic mode.
The ‘vDos’ solution would be to maintain a variable extended ASCII table. But I don’t know how many positions are free/reusable, should be at least 87 (the total of all Thai characters). Assuming it’s indeed 87, you could only have 87 different Thai character combinations on screen at any time. Major obstacle would of course be I don’t have your program, don’t know Thai and it involves a lot (too much) work…
Jos
|
|
|
Post by zetathix on Nov 12, 2018 17:47:17 GMT 1
I forget to tell you that NTVDM doesn't need thai driver I mention, it can be shown by its own like the upper image I posted. But I just don't understand why it can.
|
|
|
Post by Jos on Nov 12, 2018 18:00:01 GMT 1
The program could be ‘hybrid’, it runs on plain DOS (needs a driver), though it can also use Windows display functions. Then you best choice would probable be to run the program in a Windows 32-bit virtual machine. Or try DOSBox with the mentioned driver.
Jos
|
|
|
Post by zetathix on Nov 12, 2018 19:06:20 GMT 1
Thank you for you answers sir. Anyway, I will continue using vDos, for now I am writing autoit script which draw GDI+ overlay over vDos windows which come out quite OK.
|
|