FiveTech Software tech support forums

... 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 by HB_CDPSELECT() For example: The differ between India, Russia and Italy. But same in ...

Seeking guidance from Experts. I created files, with names encoded with different codepages like this using Harbour. (not xHarbour) function NatCreate()   local aFiles := { "Own", Chr(196)+Chr(197)+Chr(198), Chr(196)+Chr(197)+Chr(198), ...

Seeking guidance from Experts. I created files, with names encoded with different codepages like this using Harbour. (not xHarbour) function NatCreate()   local aFiles := { "Own", Chr(196)+Chr(197)+Chr(198), Chr(196)+Chr(197)+Chr(198), ...

It does not matter whatever codepage the file names are encoded or the contents of the file are encoded. Here is a sample to copy files matching the mast "My*File.txt" contained in the source folder "c:\natfiles\src\" ...

We do not need any help.
We are very clear.
Please wait for our posts and then only please respond.
Btw, OSP 8859-1 is the same as PTISO, which is similar to 1252 ANSI codepage.

... set HB_SELECT("PT850") and it will be restored. No point keep testing. The problem 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 ...

... set HB_SELECT("PT850") and it will be restored. No point keep testing. The problem 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 ...

... the problem with console too, so no FWH, and with Harbour too. For this, I don't believe 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 ...

... set HB_SELECT("PT850") and it will be restored. No point keep testing. The problem is 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 ...

... set HB_SELECT("PT850") and it will be restored. No point keep testing. The problem 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 ...

... the problem with console too, so no FWH, and with Harbour too. For this, I don't believe that both Harbour and xHarbour could have bugs in the codepage system. I believe that the problem is in your sample, but I have not enough knowledge about codepages to say more, sorry. Any ideas? I can ...

If PTISO is working fine for you, why can't you use it? Why doesn't it make sense, if in all other versions of FIVEWIN, the command SET(_SET_CODEPAGE,"PT850") works and in this new version it no longer works in: FWH24.09. He understands? Por qué no tiene sentido, si en todas las demás ver...

Enrico, xHarbour's CODEPAGE.LIB is infinitely SMALLER than HARBOUR CODEPAGE.LIB, can you compare them? Enrico, CODEPAGE.LIB de xHarbour es infinitamente MÁS PEQUEÑO que CODEPAGE.LIB de HARBOUR, ¿puedes compararlos? Enrico, you participated ...

Good morning Master Nages, I don't know what changed in CODEPAGE.LIB, my question is what should I use now for the Portuguese language: Buenos días Maestro Nages, no sé qué cambió en CODEPAGE.LIB, mi pregunta es qué debo usar ahora para el idioma portugués: ...

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 ...