But I'm slighlty disappointed as I misunderstood Azhrei and thought that he would "debug" the macro engine too
Things like these that don't work and are sometimes show stoppers for us, accentuated alien fools :
Code: Select all
[var1="éàù"]
Moderators: dorpond, trevor, Azhrei, Craig
Code: Select all
[var1="éàù"]
Heh, and hopefully "expected" means "correctly"!!patoace wrote:Tested Tables, campaign properties, tokens and campaign files. All working as expected.
LOL -- I didn't even know that was a problem!Natha wrote:Things like these that don't work and are sometimes show stoppers for us, accentuated alien fools :
Ok, thanks for looking at it.Azhrei wrote: And that's part of the parser -- really not my bailiwick. I'm guessing that the parser has some kind of single-byte limitation. I'll take a look, but all I was looking at was the file I/O portion of it.
Natha wrote:Ok, thanks for looking at it.Azhrei wrote: And that's part of the parser -- really not my bailiwick. I'm guessing that the parser has some kind of single-byte limitation. I'll take a look, but all I was looking at was the file I/O portion of it.
On another subject, there is still a bug in b73 : a PC token saved is always reloaded as NPC (when dropped from the ressource library.
Azhrei, thanks again for all your work! This is truly fantastic, and your work seems to be progressing at a very nice and smooth pace.Azhrei wrote:LOL -- I didn't even know that was a problem!Natha wrote:Things like these that don't work and are sometimes show stoppers for us, accentuated alien fools :
And that's part of the parser -- really not my bailiwick. I'm guessing that the parser has some kind of single-byte limitation. I'll take a look, but all I was looking at was the file I/O portion of it.
I'm going to finish the version number thing and post a build, then I'll look at the parser...
It appears that the current ANTLR library we're using (2.7.6) does not 100% support Unicode and therefore the lexer (the component that reads text) doesn't either.Natha wrote:Ok, thanks for looking at it.Azhrei wrote: And that's part of the parser -- really not my bailiwick. I'm guessing that the parser has some kind of single-byte limitation. I'll take a look, but all I was looking at was the file I/O portion of it.
This is fixed in b74 (it's already in SVN).On another subject, there is still a bug in b73 : a PC token saved is always reloaded as NPC (when dropped from the ressource library.
There has also been a significant change in the syntax that is used to define grammars between ANTLR 2 and 3. You would have to rewrite the grammar if you wanted to update the version.Azhrei wrote:It appears that the current ANTLR library we're using (2.7.6) does not 100% support Unicode and therefore the lexer (the component that reads text) doesn't either.Natha wrote:Ok, thanks for looking at it.Azhrei wrote: And that's part of the parser -- really not my bailiwick. I'm guessing that the parser has some kind of single-byte limitation. I'll take a look, but all I was looking at was the file I/O portion of it.
ANTLR 3.x (currently 3.2) does support Unicode but it has a slightly different Java interface. I will look at this to see how much work it would be to drop in v3.2 and make it work. Don't hold your breath.
That would be extra super cool, I'm officialy holding my breath now.Azhrei wrote:ANTLR 3.x (currently 3.2) does support Unicode but it has a slightly different Java interface. I will look at this to see how much work it would be to drop in v3.2 and make it work. Don't hold your breath.
Well, given that MTscript is on its way out, this probably isn't worth the effort.Craig wrote:There has also been a significant change in the syntax that is used to define grammars between ANTLR 2 and 3. You would have to rewrite the grammar if you wanted to update the version.
Yep ... that sad but logicalWell, given that MTscript is on its way out, this probably isn't worth the effort.
The problem is when using a framework like DevientNull's, all the flavour texts and other non numeric data from powers are stored in JSON/variables/whatever ... At best, the accent is replaces by "square" character, at worst the macro doesn't workpatoace wrote: But meanwhile, do you have some specific place where you want accented characters, Natha? I have found workarounds to make this issues almost invisible to my players and I do like my ñs and ¿s
Yeah, that's a problem because if you are using a framework, you'd have to write all the framework with the international characters in mind.Natha wrote:The problem is when using a framework like DevientNull's, all the flavour texts and other non numeric data from powers are stored in JSON/variables/whatever ... At best, the accent is replaces by "square" character, at worst the macro doesn't workpatoace wrote: But meanwhile, do you have some specific place where you want accented characters, Natha? I have found workarounds to make this issues almost invisible to my players and I do like my ñs and ¿s
We have the option to replace all accents by the equivalent HTML code but it's a PITA to write (for once) and even sometimes it's not correctly replaced in the output (HTML frame or chat) : a ";" is sometimes still printed (but I don't really get the how and when of it).
I honestly recommend not going that route. It is much better to have an all-Unicode accepting code base internally than to cover this up via patching things on the macro side in your framework with re-translating/patching all variable content through subroutines.patoace wrote:Yeah, that's a problem because if you are using a framework, you'd have to write all the framework with the international characters in mind.
As I mentioned above -- and as has been discussed here many times -- 1.4 will at some point deprecate MTscript in favor of JavaScript, probably with both of them co-existing for some amount of time. JS doesn't have any problems with Unicode.LeopoldVonRanke wrote:It seems that, if the Lords of coding find it too intensive to transfer the code to a framework that handles Unicode universally, it must wait -- but that feature should definitely be on the list for 1.4!
Won't work. There's no way to get the accented characters into the string in the first place. Hence the problem.[...] maybe we can code an opensource macro lib that translates strings with international characters into correct html display symbols?