[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: KDE Glossary
From:       Frerich Raabe <frerichraabe () gmx ! de>
Date:       2001-05-01 1:28:56
[Download RAW message or body]

On Monday 30 April 2001 17:36, Stephan Kulow wrote:
> On Monday, 30. April 2001 15:39, Frerich Raabe wrote:
> > On Monday 30 April 2001 15:13, Stephan Kulow wrote:
> > > On Monday, 30. April 2001 14:48, Frerich Raabe wrote:
> > > > I've been working on a KDE-wide glossary lately (which bases on the
> > > > glossary used on http://www.kde.de). I uploaded the current docbook
> > > > file to http://frerich.derkarl.org/glossary.docbook so that those who
> > > > are interested can have a look. Two issues have come up so far:
> > > >
> > > > a) As I expect the glossary to become rather big as people add
> > > > entries, I divided it into several sections, each section
> > > > corresponding to a letter in the alphabet. This might become
> > > > problematic for the translators as the translated expressions
> > > > probably start with a different letter and should therefore be moved
> > > > to the respective section of the glossary. This is only possible by
> > > > editing the docbook by hand, so the po2xml stuff cannot be used for
> > > > the glossary AFAICS. Any ideas how to solve this?
> > >
> > > I think doing sorting by alphabet is a bit nonsense, sorting by logical
> > > groups makes much more sense if you want to sort at all. Sorting by
> > > alphabet can be done by some software using this glossary.
> >
> > I think sorting by logical groups isn't really useful if you don't know
> > what group the expression belongs to. I just asked my sister, she knows
> > nothing about "Widget" but that it starts with "W", so that information
> > should IMHO be sufficient to lead her to the explanation.
>
> Of course, but your sister doesn't read the glossary.docbook file, but uses
> an application showing it to her. That application can do the search
> functionality for her.

I just noticed another potential issue: the docbook glossary is, as I 
mentioned, not only going to be used with KHelpCenter but also for the 
websites of the translation teams. In case the glossary grows as fast as we 
expect, the current PHP-based solution to transform the XML-like input into 
HTML might turn out to be too slow in the near future.

If the entries in the docbook file aren't sorted already, the PHP stuff would 
have to do that on the fly, which would make things even more slower and 
lower the bar above which things become slow.

- Frerich

-- 
int m,u,e=0;float l,_,I;main() {for(;e<1863; putchar((++e>924&&952>
e?60-m:u) ["\n .:ed.xmg@ebaarhcirerf:.   ]"])) for(u=_=l=0;(m=e%81)
<80&&I*l+_*_ <6&&25>++u;_=2*l*_+e/81*.09-1,l=I)I=l*l-_*_-2+.035*m;}

[prev in list] [next in list] [prev in thread] [next in thread]