Diacritics break

[fabiocm]

Why doesn't Fantasy Grounds accept special characters in character functions and macros? I honestly always thought this was a known issue that would eventually get fixed, but it's still exactly the same to this day. It would be great to be able to write some variables in my own language, but whenever the parser encounters something as simple as a 'ç', 'ñ', 'á', or any other such diacritic, it just breaks.

[LordEntrails]

Are you trying to use supported characters? You can get details of what characters are supported, as well as how a lot of this is not in the control of SmiteWorks. Start with this post and go through the thread from there. https://www.fantasygrounds.com/forums/showthread.php?58976-Unicode-Support&p=625231&viewfull=1#post625231

[fabiocm]

As far as I know, they are supported characters. I'm mainly writing words like "bênção", "rápido", and others that use diacritics like these.

[LordEntrails]

Is it in an extension/ruleset code that you are adding these? i.e. in the LUA or XML itself? Or is this in a module where you are just adding content?

[fabiocm]

It is custom content. I'm creating a new creature and I'm using my own language.

[LordEntrails]

It works.
66688

If you read in the earlier thread I linked you will find that in some situations, non-English language keyboards don't work. Cut and Paste, the way I did the image, always works. It has to do with something between the operating system and Unity and isn't something SmiteWorks can fix for Fantasy Grounds.

[fabiocm]

Oh, my bad, I think I misspoke. Accents and other diacritics show up when I type.

The problem I'm referring to is with automation and dice rolling, like in the attached video. When there's a diacritic in the word, it cuts off the word. Some special characters also do this (like the ♦, which is an alternative to the Starfinder action symbol).

[superteddy57]

All rulesets focus on english to accomplish most of it's automation. Some rulesets can take advantage of using string resources to accomplish those tasks with other languages. Replacing the string resources as an extension may help in this case. Just depends on how the automation was setup.

[Trenloe]

The problem I'm referring to is with automation and dice rolling, like in the attached video. When there's a diacritic in the word, it cuts off the word. Some special characters also do this (like the ♦, which is an alternative to the Starfinder action symbol).
Regarding the action symbol, I'd recommend converting to use the recognized action symbol characters - details here: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/996643360/PFRPG2+Action+Symbols

Regarding the parsing of the attack line - the FG code relies on LUA pattern matching to extract data from the potentially complex attack strings. In this was %w is used - which is "all alphanumeric characters", so this appears to be a limitation with the built in LUA libraries (probably) or how string data with these types of characters is passed to them. EDIT: I don't know if a fix for this is possible as further investigation seems to suggest that %w is only ASCII alphanumeric characters.

Details on LUA pattern matching here: https://www.lua.org/manual/5.1/manual.html#5.4.1