On Sunday 16 September 2007 21:33, David Bruce wrote:
> It has more things broken than I would like, certainly.
"release early, release often" :)
> > 1. I tried to select a german game, but it looped endlessly..
> Looked at this one - it is because the German keyboard.lst doesn't have
> some of the characters in the selected word list, so tuxtype thinks that
> these chars cannot be typed and goes back to the menu.
> The program now relies heavily on each theme's "keyboard.lst" to decide
> what characters are needed and should be pre-rendered. The old way was
> just to render everything for chars 0-255, which precluded i18n to
> non-Western languages that use Unicode chars outside that range.
> The new scheme seems to be error-prone, but should be OK once we get a
> correct keyboard.lst in place for each language. I'd really like to be
> able to query the OS to find out what Unicode chars are typeable with the
> user's current keyboard setup, but I don't know how to do that. At least
> I'm pretty sure that SDL doesn't have a cross-platform way to do that.
Ah. Thanks for the explaination. Once 1.5.15 is in unstable and build (for =
main arches) I intend to send a mail to debian-i18n@... to get native=20
speakers to review the translations, keyboard.lsts and word-lists, to polis=
> > 2. The new tuxtype-data binary package doenst include any fonts, but
> > instead depends on ttf-sil-andika, ttf-sil-doulos and
> > ttf-malayalam-fonts. What is ttf-sil-doulos used for?
> Russian - however, there isn't a valid Russian/Cyrillic keyboard.lst, so =
> could inactivate this theme until we get one.
Ah. I'd say, let's keep it. This way it's easier for someone to just fix th=
keyboard.lst, rebuild and see if it's working now.
> So, when the list of themes is being generated, we should check to see if=
> non-default font is requested, and only display the theme as a choice if
> the font is available - sounds like a good idea and shouldn't be too much
> I don't know about "key.png", but the others are "overrides" of the
> corresponding files under data/images that are translated into Malayalam.
Ah. key.png is also an override image.
Now we need to document the copyrights of those modified images...
> > 4. /usr/share/tuxtype/data/themes/malayalam/scripts/ includes a bunch of
> > xml files, which no other language has. or is this because indic
> > languages are so different? At least projektInfo.xml doesnt look like i=
> > needs to be duplicated...
> I think Mobin and colleagues are just including some xml lesson content in
> their theme. I haven't really looked at these files.
> > 5. 1.5.14 has a lot more files compared to 1.5.6:
> These mostly reflect the addition of the Brazilian-Portuguese theme and
> making sure all themes have a keyboard.lst. Also, "settings.txt" is a
> place for theme-specific settings - this is how themes specify a needed
> font, although it could also be used for other settings.
Ah, thanks again for explaining :)
> It turned out that supporting char values beyond 255 required that *lots*
> of things be changed or replaced, and it is taking a while to clear up the
> resultant problems.