|
|
Post by bbahes on Feb 21, 2021 20:36:58 GMT 1
Hi! I'm trying to help customer to run it's old DOS apps in Windows 10 environment. I'm able to run apps but I'm missing Croatian characters in application:  In old MS-DOS they used some utility apps to emulate Croatian letters. However running those utility apps does not change keyboard layout nor does it change it visually in app. Can anyone suggest what to enter in autoexec or config.sys to get Croatian characters? Or what to do for utility apps? Thanks in advance! Regards. |
|
|
|
Post by Jos on Feb 21, 2021 21:16:56 GMT 1
Localized characters are eventually in the ASCII 128-255 range. The characters you highlighted are however below that.
Start with a clean (empty) autoexec.txt and config.txt. Enter some Croatian letters at the command prompt. If they don’t display correctly, check the codepage with CHCP. It should be 852 or 1250 (?), eventually change that by CHCP 852 or 1250. If some characters are still incorrect, add the line FONT = - to config.txt, and restart vDos.
Jos
|
|
|
|
Post by bbahes on Feb 21, 2021 23:08:09 GMT 1
Localized characters are eventually in the ASCII 128-255 range. The characters you highlighted are however below that. Start with a clean (empty) autoexec.txt and config.txt. Enter some Croatian letters at the command prompt. If they don’t display correctly, check the codepage with CHCP. It should be 852 or 1250 (?), eventually change that by CHCP 852 or 1250. If some characters are still incorrect, add the line FONT = - to config.txt, and restart vDos. Jos Tried 852 and got "most" letters by typing in command prompt, however, not in application. They remain like in first screenshot. I tried FONT = - in config.txt, but no result. Do I need to put path to font after - ? |
|
|
|
Post by Jos on Feb 21, 2021 23:21:52 GMT 1
No, the minus sign only tells vDos not to translate some 128-255 ASCII characters to line segments.
If the characters are correct at the command prompt. But not in your application, it seems to use a non-standard implementation of (lower) ASCII characters, also relying on non-standard support programs to do the translation.
If the application still displays incorrect characters, w/o any support program loaded, it ends for vDos.
Jos
|
|
|
|
Post by bbahes on Feb 21, 2021 23:31:57 GMT 1
No, the minus sign only tells vDos not to translate some 128-255 ASCII characters to line segments. If the characters are correct at the command prompt. But not in your application, it seems to use a non-standard implementation of (lower) ASCII characters, also relying on non-standard support programs to do the translation. If the application still displays incorrect characters, w/o any support program loaded, it ends for vDos. Jos Thanks! Trying to load some of those utility apps to convert font but no luck...   They used these apps to display Croatian characters in app. Is there a way to find out why they are not working? |
|
|
|
Post by Jos on Feb 21, 2021 23:50:21 GMT 1
vDos uses TTF fonts, those don’t mix with bitmap fonts. An utility to load a bitmap font into the VGA card has no effect. Nor any subsequent utility translating ASCII characters based on former utility.
If the application doesn’t display the characters correctly w/o those utilities, it ends for vDos. Would be a first, due to a completely non-standard (and weird) solution to handle localized characters.
Jos
|
|
|
|
Post by bbahes on Feb 22, 2021 0:06:07 GMT 1
vDos uses TTF fonts, those don’t mix with bitmap fonts. An utility to load a bitmap font into the VGA card has no effect. Nor any subsequent utility translating ASCII characters based on former utility. If the application doesn’t display the characters correctly w/o those utilities, it ends for vDos. Would be a first, due to a completely non-standard (and weird) solution to handle localized characters. Jos I agree on "weird" part. These apps where built in early 90's for Croatian market...and without fonts with Croatian characters back then I guess this was only solution. Thanks though for your prompt replies and help! Regards. |
|
|
|
Post by aintnomistery on Dec 27, 2021 14:50:14 GMT 1
I hope it is not too late.
The easiest way for this is not to change anything in databases. It is an old YUSCII code, from the eighties.
Just, use the TTF font which is fixed for that. I have some LUCINDA which works for me for years. In CMD properties you can change this with a little tweak in the registry.
|
|
