Hi there.
I'm trying to run the Wordstar word processor with vDos on Win7 x64. The program itself runs fine, but I have a problem loading a localized font. The char set is specific because it uses chars from two local languages. The way it's supposed to work (and it does on Win XP withhout vDos) is that first i load a font named forum.f16 with a program called Vgamax and than run a program called keyforum.com which adds the local characters to the font. I suspect that keyforum.com was specially written for just this font. The problem is that when running Wordstar in vDos the specific local characters don't get displayed, I'm guessing the built-in TTF font overwrites them. Is there a workaround this? Since there is no ttf verison of forum.f16 could you tell vDos not to use the built-in ttf but whatever the system provides? Or would that just make the whole thing look upscaled and blurry like in DOSBox (in which the font display as it should)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Code page 437
The characters that are displaying correctly (but only when I select hungarian in the language bar): íöüóúéá and CAPS ÖÜÉ
Characters not displaying: ő (displaying Q instead), ű (q), Ő(P), Ű(p), Í(ascii 205), Á(ascii 193), Ú(ascii 218), Ó(like the other, cant find the code for it).
Serbian characters are not displaying at all: ćčšđž + Caps
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After adding CHCP 1250 to autoexec.txt (ABOVE the line that runs your program), remove all references to the custom font.
You should also install another font like CONSOLAS (see config.txt for details) that has all the required characters.
Again, your custom font will not appear. But, as Jos says, CHCP 1250 in autoexec.txt and an external font like Consolas will make all these characters appear.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks guys. This way I can type the chars, but those are not the same chars as in the custom font. The text files are opened and edited on other computers that use the custom font, so I can't use something different. Guess I'll use DOSBox.
Gabor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Read the config.txt again on how to select another font (Consolas).
font = consola
This line has to be in config.txt and the Consola.ttf file has to be copied to the vDos folder.
Some examples of Alt+ASCII code I get at the vDos command line:
I'm not sure we understand each other. I activate the Consola font (tried with others too), switch the code page and run Wordstar. I can type the local characters just fine, but internally Wordstar recognises them differently than those from the custom font. When I open files typed earlier this way some of the local chars are not displayed correctly, also if I open the newly typed files in DOSBox (with the custom font acivated) some of the local chars are not displayed correctly.
The files later get converted and used in a DTP program, but the converter is programed for the custom font, it won't work with anything else. So I have to use the custom font.
Your solution works, I just can't apply it in my situation.
Gabor
Last edit: Anonymous 2014-11-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could try to make a custom TTF font with the right characters that correspond to what you want to see. This is not so difficult, contact me at lexitec@lexitec.fi for details.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi there.
I'm trying to run the Wordstar word processor with vDos on Win7 x64. The program itself runs fine, but I have a problem loading a localized font. The char set is specific because it uses chars from two local languages. The way it's supposed to work (and it does on Win XP withhout vDos) is that first i load a font named forum.f16 with a program called Vgamax and than run a program called keyforum.com which adds the local characters to the font. I suspect that keyforum.com was specially written for just this font. The problem is that when running Wordstar in vDos the specific local characters don't get displayed, I'm guessing the built-in TTF font overwrites them. Is there a workaround this? Since there is no ttf verison of forum.f16 could you tell vDos not to use the built-in ttf but whatever the system provides? Or would that just make the whole thing look upscaled and blurry like in DOSBox (in which the font display as it should)?
Have you tried using another font like Consolas in vDos?
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Yes, I tried different fonts, it doesn't help.
What is the current code page reported by CHCP at the vDos command line.
And what acharacters don't display correctly?
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Code page 437
The characters that are displaying correctly (but only when I select hungarian in the language bar): íöüóúéá and CAPS ÖÜÉ
Characters not displaying: ő (displaying Q instead), ű (q), Ő(P), Ű(p), Í(ascii 205), Á(ascii 193), Ú(ascii 218), Ó(like the other, cant find the code for it).
Serbian characters are not displaying at all: ćčšđž + Caps
Code page 437 is US international, add CHCP 1250 to autoexec.txt.
Jos
Edit: replaced with a different message.
Last edit: Edward Mendelson 2014-11-23
After adding CHCP 1250 to autoexec.txt (ABOVE the line that runs your program), remove all references to the custom font.
You should also install another font like CONSOLAS (see config.txt for details) that has all the required characters.
Again, your custom font will not appear. But, as Jos says, CHCP 1250 in autoexec.txt and an external font like Consolas will make all these characters appear.
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thanks guys. This way I can type the chars, but those are not the same chars as in the custom font. The text files are opened and edited on other computers that use the custom font, so I can't use something different. Guess I'll use DOSBox.
Gabor
And with CHCP 852?
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Basicly the same.
Read the config.txt again on how to select another font (Consolas).
font = consola
This line has to be in config.txt and the Consola.ttf file has to be copied to the vDos folder.
Some examples of Alt+ASCII code I get at the vDos command line:
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I'm not sure we understand each other. I activate the Consola font (tried with others too), switch the code page and run Wordstar. I can type the local characters just fine, but internally Wordstar recognises them differently than those from the custom font. When I open files typed earlier this way some of the local chars are not displayed correctly, also if I open the newly typed files in DOSBox (with the custom font acivated) some of the local chars are not displayed correctly.
The files later get converted and used in a DTP program, but the converter is programed for the custom font, it won't work with anything else. So I have to use the custom font.
Your solution works, I just can't apply it in my situation.
Gabor
Last edit: Anonymous 2014-11-25
I’m also afraid we misunderstand each other.
I expected Robert Sawyer, the WordStar expert, would join in to shed some light on your problem.
Jos
Gabor,
You could try to make a custom TTF font with the right characters that correspond to what you want to see. This is not so difficult, contact me at lexitec@lexitec.fi for details.