Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Нi! How I can add Russian support (for example the coding "ru_RU.KOI8-R") in source files that after compilation the executed file CLIPSWin.exe understood the Russian coding in values of variables, the facts, comments, in titles of functions and in names of variables?
I looked at this briefly when I added internal support for unicode in version 6.3. The CLIPSWin interface code uses the old Win32 APIs and it wasn't immediately apparent how to add support for other character encodings.
Hello, and except of CLIPSWIN, the Clips core should be capable of processing Russian language namely in facts? Or what should be done ?
CLIPS does not support non-ASCII character encodings.
so … is it unreal make dialog with user in Russian or someone find decision?
and it used to work with Cyrillic, is not it?
it used to work, but now it doesn`t…what had happened with it ? …
Look at https://sourceforge.net/projects/clipsrules/forums/forum/776945/topic/4735107 … with CLIPS 6.30 it works (with CLIPS 6.24 it does not) for both fact names and for string values. The only thing is a correct handling of characters in printRouter() and in calling EnvAssert(). It depends on from what environment You use CLIPS.
The exact same executable used to work with Cyrillic or one version worked with Cyrillic and a newer one does not?