I'm not good at Linux :) I tried but the constant error is missing a library, then the other ...MOD wrote:Would you test it on a russian linux version?
I'm a bad Linux-tester
I'm not good at Linux :) I tried but the constant error is missing a library, then the other ...MOD wrote:Would you test it on a russian linux version?
I was able to run on Linux, but wxFBE it does not work with Cyrillic.MOD wrote:Did you read the readme? Or do you know some linux users which could test it. I can't fix this issue for windows when I'm not sure, it will work on linux too.
I would test it but I don't speak russian and can't read any Cyrillic.
That's no good idea for cross-platform code : )MOD wrote:That's why I can't simply use WinAPI.
FB can handle it. But you need consoles on each platform that supports the character encoding used in FB.MOD wrote:If you can manage to get a correct string with just FB (or wx-c) in console, you could post it here. I really don't know how to handle this issue to get it work on all platforms.
Don't you mean ncursesw? libintl doesn't handle platform specific output at all, but basic encoding conversions on *nix systems??!?TJF wrote: For good I18N support in FB it's wise to use libintl. This works with UTF-8 encoding. UTF-8 is standard on most *NIX systems but it's hard to find a wondiws console that supports it.
do you use the 0.24 fbc version from Mon Aug 20, 2012 to build wxFBE ?
fbc -version wrote:FreeBASIC Compiler - Version 0.24.0 (08-19-2012)
Exactly. I don't need a console version but it would help. I tested with our german Umlaute and it works with just FB commands and with just wx-c, and due to the lack of russian skills, I can't test it.That's no good idea for cross-platform code : )
We're talking about russian language and cyrillic letters for the app mentioned in the subject.marcov wrote:Don't you mean ncursesw? libintl doesn't handle platform specific output at all, but basic encoding conversions on *nix systems??!?TJF wrote: For good I18N support in FB it's wise to use libintl. This works with UTF-8 encoding. UTF-8 is standard on most *NIX systems but it's hard to find a wondiws console that supports it.
This is the point. I recomment not to use different character encoding! Go with a system that uses the same encoding in source code and in the GUI (console doesn't matter, it's for debugging only - use any language here).MOD wrote:It have to work with pure FB and wx-c, I won't use any additional library for this! And even if I would, I have to convert any string between FBString, wxString and that additional String-type and this is the next big issue with using another lib.
I got sidetracked by the "console" thinking it was about the console, but the basic problem still stands.TJF wrote:We're talking about russian language and cyrillic letters for the app mentioned in the subject.marcov wrote:Don't you mean ncursesw? libintl doesn't handle platform specific output at all, but basic encoding conversions on *nix systems??!?TJF wrote: For good I18N support in FB it's wise to use libintl. This works with UTF-8 encoding. UTF-8 is standard on most *NIX systems but it's hard to find a wondiws console that supports it.
No. mdLanguage and also libintl serve STRINGs in different languages and the problem showing native characters in the console are the same. If the console supports UTF-8 there's no problem. But an FB screen doesn't support it.MOD wrote:Will libinlt work better with a console than mdLanguage?
iconv can be used to translate between different character sets. It's used by libintl on wodniws.marcov wrote:It doesn't matter if you have an UTF8 string containing cyrillic, obtained from libintl, if you then pass it to an API that doesn't understand UTF8.
I tried the regular expression engine as provided with scintilla and.... it's lightweight at best. No support for \w, \d etc...,MOD wrote: My fault! The checkboxes exist already and the options are working but in code I did a 'If 0 Then' instead of the actual code. I fixed it and uploaded a new package (download at FreeBASIC-Portal, see first post). wxRegEx is not part of wx-c but the search engine can use some RegExp (that's why there's a checkbox for it and no need for pcre). Here a link for what works with it: RegExp in wxFBE.
I know. We support iconv as a fallback, on Windows even. (there are some problems with the missing of errno in some versions that require different allocation schemes though, since the E_TOOBIG (or something like that) can't be used to conservatively allocate)TJF wrote:iconv can be used to translate between different character sets. It's used by libintl on wodniws.marcov wrote:It doesn't matter if you have an UTF8 string containing cyrillic, obtained from libintl, if you then pass it to an API that doesn't understand UTF8.