-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syntax: support for extended characters #212
Comments
Since $ $(go env GOPATH)/bin/1pl
Top level for ichiban/prolog v0.10.0
This is for testing purposes only!
See https://github.com/ichiban/prolog for more details.
Type Ctrl-C or 'halt.' to exit.
?- 改善.
2022/07/16 13:43:08 error(existence_error(procedure,改善/0),root)
?- プロログ.
2022/07/16 13:43:15 error(existence_error(procedure,プロログ/0),root)
?- はい.
2022/07/16 13:44:34 error(existence_error(procedure,はい/0),root) |
For Korean letters I get:
(Warning, I am really not an expert in Unicode at all). It seems that you can treat all |
... It seems that you can treat all letters that are qualified as |
Seems like ?- write('あー').
2022/08/01 05:22:09 failed to query: unexpected token: {invalid 'あー} Works in v0.9.1. |
Fixed in v0.10.4! $ $(go env GOPATH)/bin/1pl
Top level for ichiban/prolog v0.10.4
This is for testing purposes only!
See https://github.com/ichiban/prolog for more details.
Type Ctrl-C or 'halt.' to exit.
?- write('あー').
あーtrue.
?- |
Even the following works:
|
In 6.5 the processor character set (PCS) is defined. It not only includes the characters defined by
char
(6.5) but also may include additional members, known as extended characters. Note that this is not an extension in the sense of 5.5.1, but is part of the actual implementation defined character set. The standard also mentions examples in NOTE 2:Now, certainly, an implementation does not have to support additional characters at all, but it seems to make a lot of sense in the times of UTF-8.
So I would expect that
is rather treated like
which also many existing implementations do.
The text was updated successfully, but these errors were encountered: