[Translators] Support for msgctxt

[Ricardo Mones]

On Tue, Nov 13, 2012 at 10:41:12AM -0200, H wrote:
> On 13/11/2012 08:57, Paul wrote:
> > On Tue, 13 Nov 2012 08:37:08 -0200
> > H <hm at hm.net.br> wrote: 
> > 
> >> looking at the big picture ...
> > 
> > OK.
> > 
> >> why would you change something without having any reasonable
> >> advantage?
> > 
> > There is a reasonable advantage. Like Andrej pointed out in the first
> > place:
> > 
> 
> well, technical issues are always discussable, but that of course is not
> my point here
> 
> most people think about localization in the way of having the interface
> translated to some local language
> 
> what then in first place makes it a developer choice (the method)
> 
> even if that is true in most cases, other cases are more and more emerging
> 
> multi-language corporate environments are becoming very usual
> 
> in larger countries, as mine which is Brazil, even in little Spain it
> happens, there are several local slangs in the same country

  Don't know about Brazil but I can assure you in Spain they are not slangs
but languages (some with their own official status).

> in such cases pot files turn out to be extremely annoying because of
> missing flexibility

  What missing flexibility are you talking about?

> php pot to php gettext evolution is a good example of easy on-the-fly
> localization/customization. The local end user or group do not need a
> developer, editing a text file and ready to go.

  That's the same it's done with po files, you don't need to be a
developer to change it or create a new translation.

> when I said the bigger picture I meant it as seeing from user
> perspective and may be you consider this opinion

  From the user perspective the interface gets localized no matter the
method the developers choose, fully transparent. This is a translator
vs developer issue, if any, no users were harmed in the making of this.
-- 
  Ricardo Mones 
  ~
  Absence of evidence is not evidence of absence.          Carl Sagan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.claws-mail.org/pipermail/translators/attachments/20121113/96d79158/attachment.pgp>