FiveTech Software tech support forums

... such files (for xHarbour). The approximate scheme is as follows

I don't think so.
Brfore I discuss this in more detail, a few points.
Results of OemToAnsi() and AnsiToOem() differ from country to country. Depend on the default Windows codepages for OEM and ANSI. These codepages can not be changed ...

... in dos-prompt:
https://imagizer.imageshack.com/v2/xq70/923/HuQ4Mh.png
We can see from the image is that the command prompt is using my default OEM codepage 437 (OEM English codepage)
Still all filenames created with different codepages are displayed correctly though different from the codepage ...

... in dos-prompt:
https://imagizer.imageshack.com/v2/xq70/923/HuQ4Mh.png
We can see from the image is that the command prompt is using my default OEM codepage 437 (OEM English codepage)
Still all filenames created with different codepages are displayed correctly though different from the codepage ...

Hi Mr. Rao,

? GetOEMCP(), GetACP()

Türkiye:
854, 1254
Thanks.
1) Please once again give me 3 or 4 unique to Turkish characters both their OEM asc values and corresponding ANSI asc values.

2) Can you please check again? Is it 854 or 857 ?
Please see this webpage:
https://learn.microsoft.com/en ...

Hi Mr. Rao,

? GetOEMCP(), GetACP()

Türkiye:
854, 1254
Thanks.
1) Please once again give me 3 or 4 unique to Turkish characters both their OEM asc values and corresponding ANSI asc values.

2) Can you please check again? Is it 854 or 857 ?
Please see this webpage:
https://learn.microsoft.com/en ...

... is only with PT850.

Users from other countries set codepage to ITWIN, ESWIN, TRWIN, etc.
All those codepages are ANSI codepages.
But PT850 is an OEM codepage. Not an ANSI codepage. The problem arose because we treated PT850 also like we treated other HB_CDPSELECT() codepages.

Anyway, the ...

... is only with PT850.

Users from other countries set codepage to ITWIN, ESWIN, TRWIN, etc.
All those codepages are ANSI codepages.
But PT850 is an OEM codepage. Not an ANSI codepage. The problem arose because we treated PT850 also like we treated other HB_CDPSELECT() codepages.

Anyway, the ...

... that both Harbour and xHarbour could have bugs in the codepage system.

There are no bugs at all in Harbour or xHarbour. I will later explain the behavior. Please be patient.

I can advice you once more to use PTISO, if it works fine for you. .
Yes, PTISO is an ANSI codepage not an OEM codepage.

... only with PT850.

Users from other countries set codepage to ITWIN, ESWIN, TRWIN, etc.
All those codepages are ANSI codepages.
But PT850 is not an OEM codepage. Not an ANSI codepage. The problem arose because we treated PT850 also like we treated other HB_CDPSELECT() codepages.

Anyway, the ...

... is only with PT850.

Users from other countries set codepage to ITWIN, ESWIN, TRWIN, etc.
All those codepages are ANSI codepages.
But PT850 is an OEM codepage. Not an ANSI codepage. The problem arose because we treated PT850 also like we treated other HB_CDPSELECT() codepages.

Anyway, the ...

Waiting for a solution with OemToAnsi() and CodePage()

Do you have problem with FWH1905 or FWH2409 only?

Please reply this first.

And as I told you several times, do not post programs or send programs,
OemAnsi functions do not work the same way in different countries, in particular between ...

Give me a small sample OEM string

DO NOT copy and paste here. That will automatically convert the string to UTF8.

Please give here a list of ASC values of each character.

Eg. If your string is
"AB"
You give me as
65,66

Please see my post.
Please give me any one of your OEM string (not more than ...

Give me a small sample OEM string

DO NOT copy and paste here. That will automatically convert the string to UTF8.

Please give here a list of ASC values of each character.

Eg. If your string is
"AB"
You give me as
65,66

Master Nages, another problem reported. the OemToAnsi() command is not working correctly.

Maestro Nages, se informó otro problema. el comando OemToAnsi() no funciona correctamente.


MsgInfo( OemToAnsi( "INDEX: TODOS OS ÖNDICES, CRIADOS COM SUCESSO!" ), ;
OemToAnsi( "INDEX: TODOS OS ÖNDICES ...

... La función WinINet() no estaba funcionando correctamente. Solucionado.

* Mejora: Nuevo método End() y mensaje hWnd en la clase TWebView.

* Samples\oemboxch.prg: Cómo ver los caracteres de un controlcaja OEM en una aplicación de Windows.

* samples\mariabig.prg: Leer y navegar una tabla con 4.1 ...