|
Post by Jos on Mar 4, 2021 19:29:19 GMT 1
Probably I lay this aside to have a look later on (and forgot)...
My initial idea was to modify the ASCII to Unicode table in a NLS file, but that is rather complicated. Edward Mendelson proposed to support an external ASCII to Unicode table.
My main concern however remains the right-to-left text orientation. In the XP samples, the English text is to the left, the Arabic text to the right. In vDos the other way around. Also the position of the Arabic words is reversed. Even if the individual Arabic characters would be displayed correctly, wouldn’t it be a textual mess?
Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 13:42:07 GMT 1
Thanks for replying back, appreciated. I'm trying to run a legacy code that use (Microsoft FoxPro 2.5 in widows 10) using vdos, the program works fine but it has a problem with Arabic language as mentioned before. The program was installed on dos operating system (when the PC start you can choose between two systems, the main system running windows xp and the other system running DOS/FoxPro). If I run the program on The main system. I get the same problem (Arabic language problem), and if I try to run the program on DOS OS. Before running the program the character code page `chcp` was 437, after running the program, then character code page `chcp` becomes 711 which means Arabic codepage. I tried to overwrite the codepage before running the program by using `chcp 711` but it gave me `invalid codepage` error. After tracking the code I came to a conclusion that the program changes the language using `nlsfunc` then change the codepage to 711. I try to run `nlsfunc` in vdos but it gave me an error. 1-When the PC start. i.imgur.com/A3Pqdyb.png2-Dos command window. i.imgur.com/AOCCP1d.jpg3-codepage before running the program. i.imgur.com/b6Wj1Vs.jpg4-when I run the program. i.imgur.com/5mX5C0g.jpg5-codepage after running the program. i.imgur.com/QdDM7B5.png6-if I try to run the program in windows xp(main OS). i.imgur.com/vYx4xqh.jpgThanks again. Skafi
|
|
|
Post by Jos on Mar 7, 2021 17:41:21 GMT 1
So codepage 711 was supported by Windows XP, not by later versions? If Windows XP had the NLS file (C_711.NLS?), you could copy and install that on the Windows 10 PC. Then use CHCP 711 in vDos?
Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 18:01:54 GMT 1
No. I meant codepage 711 is supported by dos only after running the foxpro program Both Windows XP and dos doesn't identify codepage 711. All I want is to run nlsfunc on vdos or windows xp and after. Info regarding nlsfunc can be found here. www.computerhope.com/nlsfunch.htm
|
|
|
Post by Jos on Mar 7, 2021 18:21:11 GMT 1
Could you submit the file that gets loaded by nlsfunc.exe?
Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 18:41:38 GMT 1
|
|
|
Post by Jos on Mar 7, 2021 19:24:56 GMT 1
Did you look for it in the FoxPro directory?
Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 19:28:11 GMT 1
Yes, nothing.
just in dos98 folder.
skafi
|
|
|
Post by Jos on Mar 7, 2021 19:37:28 GMT 1
Publish that FoxPro directory and I'll have a look.
Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 19:57:39 GMT 1
|
|
|
Post by Jos on Mar 7, 2021 21:41:12 GMT 1
I have to disappoint you. The found ‘documentation’ is quite confusing, it’s mostly about Clipper, not FoxProX. First NAF.COM in the naf42 directory is started. That starts NAF.CMS, w/o a known (executable) extension, vDos hands it over to Windows to process. If I temporary disable that and let it execute as a .COM file, this is displayed: NLSFUNC.EXE is not used at all, the NAF.COM and NAF.CMS combo will try to modify the DOS inners directly. Since there is no 16-bit DOS code in vDos, that is deemed to fail. Even if the translation of individual characters would be done by vDos, that still doesn’t suffice. The right-to-left orientation isn’t implemented: Jos
|
|
|
Post by mahmoudskafi on Mar 7, 2021 22:05:34 GMT 1
Ohh, I'm sorry for wasting your time on it and for that I'm thanks full <3 last question tho, can we run the program on DOS operating system as they did with windows xp, and maybe that works. as showing in the image: i.imgur.com/A3Pqdyb.pngBig help, thanks. skafi
|
|
|
Post by Jos on Mar 7, 2021 22:31:55 GMT 1
You could turn the Windows XP PC into a virtual one on Windows 10, by using for instance VirtualBox. A virtual XP will probably do better than a virtual DOS for the ease of use.
Jos
|
|