I have found a couple of i18n bugs in TSVN, but as I usually use linux
command line svn, and the bugs are not so often manifested, I have
ignored them till now. However, other people in the team (I am admin)
are getting more and more at me :-) Reporting them together as they are
closely related, I think.
At the moment we are using version 1.2.2 on updated Windows2000 Japanese
version, but these bugs are present since 1.2.0 and before. I have
tested en, jp and bg language packs so far.
1. Improper display/font of non-ASCII filenames in revision graph window
This is manifested when we have Japanese filenames under TSVN and
decide to make a revision graph. non-ASCII symbols are displayed as squares.
The interesting part is that if I export the file as WMF (couldn't
export png!) and open it in Word, it is displayed correctly (in
Japanese). No idea what is inside a WMF, but...
2. Improper display/font in blame window
This is more like wrong/default encoding set to the displayed file, but
might be just wrong font. (log msg popups show correctly in Japanese)
No workaround at this time (cannot set the font directly).
3. Problem with double-with Cyrillic with bg langpack
This is often met problem on Japanese (and other CJK?) OSes (even linux
:-( All dialogs and TSVN menus are displayed with double width Cyrillic
font, no matter what font I use.
No idea how to fix that in Windows.
4. Problem with font/encoding in dialogs during the install of bg
langpack on Japanese Windows
I know that is tough, just don't say I am not supposed to do that (bg
on ja OS). I guess the OS vendor thinks so, anyway (otherwise there
would be no Japanese OS, just ja_JP locale :-D ).
This is the least priority anyway, but the normal way to fix it seems
to have multi-lingual install program (with MSGs in all available
languages). Or move the installation from inside TSVN (overkill and too
Some thoughts about fonts...
I understand TSVN and TM are two relatively separate programs, but to
have to change the font display in two very different menus, at
different times is PITA and an overkill probably. (A usual usability
problem with any GUI). And if you plan to fix 1 and 2 by adding another
two sets of font/language, please consider again. Or at least group all
the preferences in one dialog, "i18n".
Another idea is to set the default font (in all places) on installing a
new langpack (please provide checkbox to manually overrule that).
Still another future idea is some kind of profiles (say language
profiles) where one defines the related properties for every language.
So far this is about i18n, I'd say pretty well done compared to other
products. I have use 3-5 (human) languages in development on a few
platforms, so i18n problems keep staying on the top of my TODO list :-|
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 5 15:41:28 2005