I try to use CLIPS and i will be glad if CLIPS is able to support Cyrillic symbols.
E.g. inside fact definition (fullName):
(Member (tagName UUK_MMC) (fullName "Участок усреднения концентратов ОАО ММК")))
But in CLIPS GUI for Windows I got the following:
(Member (tagName UUK_MMC) (fullName "УчаÑток уÑÑ€ÐµÐ´Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð½Ñ†ÐµÐ½Ñ‚Ñ€Ð°Ñ‚Ð¾)
Is it possible to fix it? I tried loading *.clp files in ANSI/UTF8 encoding.
Thanks for you help!
CLIPS 6.3 supports UTF-8, but the CLIPS Windows GUI which is layered on top of CLIPS does not (it's based on very old Windows APIs). The CLIPS 6.4 Windows GUI supports UTF-8.
Related
I'm coding a spanish expert system, so I have to print words with letters "ñ" or "á,é,í" or "¿" and cannot figure it out yet, is there a way to do it?
This is probably an issue with your terminal. Where are you running your programs? The best solution might be to search google for issues specific to your coding environment. (For example, I'm on macOS, my terminal has no issues with this.)
Also, if you just want a quick solution, most languages have support for Unicode-encoded strings. For example, here's how you would do it in Python (note, ñ is 361 in octal Unicode):
>>> print('ni\361o')
niño
However, if your issue persists I would recommend you try searching for users who had similar problems who also use your coding environment. I hope you're able to find a solution :)
Starting with version 6.3, CLIPS provides internal support for UTF-8 strings. So if you're using a text editor that supports UTF-8 encodings you can write programs with languages using diacritical marks (such as Spanish), other non-Latin characters sets with a small alphabet (such as Russia), and languages with complex glyphs (such as Japanese):
(deffacts hello
(hello "Hello World")
(hello "Привет мир")
(hello "مرحبا العالم")
(hello "你好世界")
(hello "ハローワールド")
(hello "여러분, 안녕하세요")
(hello "Olá Mundo"))
(defrule hello
(hello ?h)
=>
(printout t ?h crlf))
Input and output of these characters sets depends on the environment in which CLIPS is run. If you run CLIPS as a terminal application on macOS or Linux, UTF-8 is supported. The macOS IDE for CLIPS 6.3 and 6.4 support UTF-8.
CLIPSJNI, http://www.clipsrules.net/CLIPSJNI.html, also demonstrates how you can embed CLIPS in an environment supporting UTF-8 (in this case Java) to take advantage of CLIPS internal support of UTF-8.
The Windows IDE for CLIPS 6.3 does not support UTF-8 I/O. It uses older Win32 APIs and was not designed with unicode support in mind. The Windows IDE for CLIPS 6.4 uses the modern .NET frameworks which support UTF-8 I/O.
By default, Windows Command Prompt does not provide support for UTF-8 I/O, but you can enable it to provide some limited support. Launch Windows Settings and click "Time & Language", then "Language", and then "Administrative language settings". In the window that appears, click the "Change system locale..." button. Check the "Beta: Use Unicode UTF-8 for worldwide language support" check box and then click the OK button. UTF-8 output support will now be enabled in Command Prompt for languages that use a single codepoint for characters (such as Spanish and Russian). Unfortunately while input for diacritical marks and non-Latin characters appear correctly when being entered, they do not appear to be correctly passed to CLIPS (as occurs when running CLIPS as a terminal application on macOS or Linux).
I am putting together an application using WPF. A designer would like to work on the look of some of the windows using a Mac.
Does anyone know if its possible edit the actual XAML file that the programme will use on a Mac? It would help a great deal.
Thank you.
Sublime Text is a good editor that includes syntax highlighting for many formats including XAML.
Version 3 includes installers for OS X (10.7 or later), Windows, and Ubuntu. (tarballs are available for other flavors of Unix.)
I am currently developing printer drivers for Mac which should support both PS (postscript) and PCL printers. I already have an idea about supporting PS (by defining custom CUPS postscript filters in the PPD, and a PDE).
What I don't have an idea about is supporting PCL printers.
a) Is PCL automatically supported by CUPS?
b) If answer to a) is YES, will my PS filter be called when printing to a PCL printer? (I add some PJL to the print data in my PS filter).
c) If anwer to a) is NO, then how should I implement support for PCL? (I need to add some PJL to the PCL data that will be sent to printer).
have you seen https://developer.apple.com/legacy/library/samplecode/SampleRaster/Introduction/Intro.html
?
After fiddling around with Xcode build paths and build settings I got it to work. Its a complete printer driver with cups backend and filter.
kind regards,
Robert
Right now I have a first gen windows phone, with 7.8 installed [Omnia 7]. It does not have proper unicode support [I'll be precise, it does not show malayalam characters, on facebook for instance]. I looked around if WP8 supports this and it seems like it doesn't.
My question is, does WP8 have proper unicode rendering? If not throughout the OS, AT THE LEAST on the browser?
http://answers.microsoft.com/en-us/winphone/forum/wp8-wpfeatures/malayalam-unicode-support-in-windows-phone-8/4d144e4f-eea4-430b-b26d-945e2d98df00
Sorry, Malayalam is not presently supported.
I did find this, though: http://malayalam4mobile.hafees.com/
I found out (though my other question) that my IME outputs Hangul Compatibility Jamo (U+3130 – U+318F) instead of regular Hangul Jamo(U+1100 – U+11FF).
So I tried asking a question in superuser about other IMEs, no replies yet.
Should I just convert it myself? What exactly does that entail? Is it too complicated? Any ideas on how to? Any help would be appreciated.
Language: Delphi
OS: WinXP
IME: Korean Input System (IME 2002)
There is no reason you could not write an interesting experimental editor control with its own built in Unicode Compose feature. However, before you did that, you might look for a way to change the configuration of the IME. This seems to be a really interesting corner-case you have to work with. I was already surprised about your other question - that Windows has the ability to handle Raw Input from keyboards.
I found that source code for something that says it is the Korean IME is available for Windows CE. You might learn something by studying it, even though it is for Windows CE rather than XP.
http://msdn.microsoft.com/en-us/library/ee491900.aspx