Some info about how the character encoding is managed in G’MIC.
- G’MIC is actually encoding-agnostic, meaning that if you write a command in a file with a certain encoding, the result should depend on what encoding is used for output.
- For instance, defining a command file like :
foo :
echo "ééé"
and invoking it in the terminal with gmic foo, should output ééé as long as the encoding used for the file and the terminal matches.
G’MIC just loads a command file as a binary file, so it does not really care about how the strings are encoded in the command file. All strings are actually stored as char* in the C++ code (so sequences of 8-bits, meaning a single “exotic” character can be encoded with several bytes, as in UTF-8 or UTF-16).
This being said, I don’t understand why
gmic echo {`'Ç'`}
won’t echo Ç at the end.
What does
gmic echo {'Ç'}
print ?