[Scummvm-devel] Translations of the About text in ScummVM

[Johannes Schickel]

On Fri, May 13, 2011 at 1:02 PM, Thierry Crozat <criezy at scummvm.org> wrote:
> On 13 May 2011 11:51, Johannes Schickel <lordhoto at gmail.com> wrote:
>> On Fri, May 13, 2011 at 11:53 AM, Thierry Crozat <criezy at scummvm.org> wrote:
>>> On 13 May 2011 10:24, Max Horn <max at quendi.de> wrote:
>>>>
>>>> The idea was to move the "burden" of having to map HTML entities to each encoding to the translator, who would know best how to map e.g. ö to the encoding of their translation. But if that doesn't ring well with people, we can ditch that. *shrug*
>>>
>>> Oh I see I missed the point. I probably read the email too quickly.
>>> But would the burden of this mapping really be a problem if it was
>>> done by the software? I just don't want to scare translators away
>>> because there are many more strings to translate, half of which should
>>> actually not need to be translated, and some of those with html
>>> entities.
>>>
>>
>> We could at least not do it in the ScummVM binary, since we have no
>> clue at all about what charset the translation uses.
>>
>
> But we have, how else would ScummVM know which font to use?
> The charset is saved in the translations data file by the
> create_translations tool and you can get it by using
> Common::TranslationManager::getCurrentCharset().
>

We know a name for the charset, which helps in what way? How do we
know the mappings of specific characters in the charsets? How do we
even know that a specific character exists at all?

If we would want to take advantage of that, we need to know the exact
encoding. So we would need to save that for *all* charsets we support,
thus if someone wants to add support for a translation using a charset
not yet known to ScummVM the translator would have to patch the source
code first. Frankly so far we only have a handful of charsets AFAIK,
so not that bad for now.

// Johannes