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

List:       kde-i18n-doc
Subject:    Re: Kst Feature Freeze
From:       George Staikos <staikos () kde ! org>
Date:       2005-04-13 14:32:29
Message-ID: 200504131032.29702.staikos () kde ! org
[Download RAW message or body]

On Wednesday 13 April 2005 05:49, Hasso Tepper wrote:
> >    Also note that the JS extension is not covered by the freeze and
> > should not be translated because it's not enabled for compile by default
> > for 1.1.0. Development will go on there to try to get it into shape early
> > for 1.2.0 and hopefully have a solid preview for gurus in 1.1.0.
>
> I'd like to commit attached patch to make sure that correct form is used,
> not the one from kdelibs.po.
>
> Actually this is quite annoying issue for Estonian at least. There are many
> more places like this. If in most cases we can use translating string in
> application.po in application specific way, it's not the case for strings
> in common_text.cpp - they just don't appear in application.po. "Left" can
> be translated in many ways depending on context and all contexts are common
> in KDE:
>
> Command move to the left - "Vasakule"
> Position ("on the left") - "Vasakul"
> Position ("the left one") - "Vasak"
>
> And add to these left arrow key ("Nool vasakule"). I'd like to go through
> all these in KDE CVS, but I'm afraid that it makes strings in kdelibs.po
> quite useless, especially in common_text context. I would add context to
> the most of these, I'm afraid.
>
> So, opinions?

   I don't mind - feel free to fix problems.  I'm the only one on the 
development team who has even really worked with i18n so it's quite likely we 
have lots of problems lurking.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
[prev in list] [next in list] [prev in thread] [next in thread]