|
From: Dan M. <mu...@al...> - 2002-08-12 04:32:31
|
There appears to be a bug in ScrollKeeper or intltool, probably the=20 former. For example, on a system where msgfmt reports that sv is 100%=20 localized, we still get some parts of the contents list file which lack=20 <title> elements. Also, if you look in the build directory at=20 cl/templates/scrollkeeper_cl.xml, some translations are also missing even= =20 though the po files are translated. Separate from tracking down that problem, how should we handle cases wher= e=20 a string is not translated and thus the translated category name cannot b= e=20 used? It looks like either Yelp or ScrollKeeper will need to be changed,= =20 probably the latter one. I guess it is reasonable to just prune the tree= =20 under any element which lacks a localized <title>. Any other suggestions= =20 for the proper behavior? -Dan On 4 Aug 2002, Mikael Hallendal wrote: > s=F6n 2002-08-04 klockan 19.00 skrev Dan Mueth: >=20 > > > Anyway, what I noticed is that the title-element on the GNOME-sect = was > > > missing (not sure why?) Help would be greatly appreciated. > >=20 > > I'm not sure what you are referring to here. >=20 > When using 'C' as locale (I guess that is what scrollkeeper falls back > to if it doesn't find the locale passed to it). >=20 > I have a section like this: >=20 > <sect> > <title>GNOME</title> > <sect> > <title>Some subsection</title> > ... > </sect> >=20 > but when I use the 'sv' (or any other I tried) locale it looks like > this: >=20 > <sect> > <sect> > <title>Some subsection</title> (of course translated) > ... > </sect> >=20 > Not sure why this happens but it ruins my use of Scrollkeeper :) > Could it be if the translation hasn't translated 'GNOME' and it doesn't > fall back to the original string? >=20 > Regards, > Mikael Hallendal >=20 >=20 |