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

List:       kde-i18n-doc
Subject:    Re: RFC: To kde.pot or not to kde.pot
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2006-04-14 7:06:28
Message-ID: 200604140906.29453.nicolasg () snafu ! de
[Download RAW message or body]

On Friday 14 April 2006 00:46, Rinse de Vries wrote:
> Op donderdag 13 april 2006 11:35, schreef Stephan Kulow:
> > Hi!
> >
> > We currently exclude the content of kde.pot from all generated pot files.
> > The idea was to avoid duplicated translations, but it caused problems in
> > the past where it wasn't possible to overwrite certain strings in some
> > apps.
> >
> > So I'd like to know if you see the benefits of it higher than the
> > problems associated with it? Because it's easy to remove that kde.pot,
> > but it would add quite some strings to translate (to KDE4 - don't worry
> > :)
>
> kde.pot, that's the file in $KDEDIR/include?
> I don't see much benefit using it, all strings present in that file can be
> easily autotranslated by kbabel (using a translation database or po
> compendium), so i would not mind if it dissappears.
>
> I never heard of kde.pot before, but it could explain some problems i
> experienced with (ofr example) the translation of 'view' in several
> applications.

> 'view' can be translated in Dutch as 'beeld, weergave, bekijken, tonen,
> weergeven, uitzicht', depending on the context of the string.

Yes, this is the main problem of kde.pot in its actual form. ("Open" is 
another typical example of this problem.)

>
> regards, Rinse

Have a nice day!
[prev in list] [next in list] [prev in thread] [next in thread]