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

List:       kde-i18n-doc
Subject:    Re: How to represent variable-length messages
From:       Rolf Eike Beer <kde () opensource ! sf-tec ! de>
Date:       2009-10-30 21:55:46
Message-ID: 200910302354.34546.kde () opensource ! sf-tec ! de
[Download RAW message or body]


Am Freitag, 30. Oktober 2009 schrieb mvillarino:
> 2009/10/30 Chusslove Illich <caslav.ilic@gmx.net>:
> >> [: Marek Laane :]
> >> Well, probably i18nc should be applied to the long text, too, because
> >> there may be slight possibility there is analogous string in somewhere
> >> else and gettext put them together; in that case it's hard to know what
> >> the "previous" is.
> >
> > I think we should avoid context (of the linking type) on the long text,
> > because I assume that shorter texts will freqently be added, or even
> > removed, at a later point. How about instead putting the long text as the
> > context of the short text, with a keyword-like prefix indicating the
> > special usage:
> >
> >  msgid "Drop the file here"
> >  msgstr ""
> >
> >  msgctxt "(short-form) Drop the file here"
> >  msgid "Drop here"
> >  msgstr ""
> 
> What if long msg had context that deserved to be considered for the
> short one also?

Well, in case you don't immediately know how to handle that you will go and 
read what you have written down as translation for the long string which you 
know because of the context. And there you'll find not only your translation 
but also the original context.

Eike

["signature.asc" (application/pgp-signature)]

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