[Seaside] Re: Seaside and gettext not exporting domain strings
johan at inceptive.be
Sun Jan 25 19:38:21 UTC 2015
We’re using gettext with +3000 strings to translate in 3 languages (for now).
I try to keep it up to date but there is some refactoring required at this point…. it works well though.
> On 25 Jan 2015, at 18:42, David Carlos Manuelda <stormbyte at gmail.com> wrote:
> Stephan Eggermont wrote:
>> David wrote:
>>> Well, in my opinion, gettext has some advantages over simple csv
>>> dictionary translations, there are tools to translate also, like Poedit,
>>> while the issue is not about if there are or not better tools.
>> I was less than impressed by POEdit.
Did you try a recent version? It has improved over the past few years.
>> For the use case we had
>> (not so large application, only a few languages), Excel was
>> definitely superior. For large translations, I'd want application
>> integration, as the texts also have to fit on the screen.
Not sure how that rimes with Excel :)
But yes, live editing of the text displayed in its context is nice, though it’s difficult to impossible to do for all text (e.g tooltips, error messages, etc…).
>> With the right abstractions, I should be able to generate
>> translation components in the web application. Both in the
>> sense as showing a translated part of a page, as in showing
>> where a text is used. That is something that seems
>> difficult to do with gettext.
I don’t see how that conflicts with gettext (as a format).
>> To me, the only advantage
>> POEdit Pro seems to have is the reuse of existing translations.
In our experience, that’s the bad part.
The advantage of POEdit is that we supply a file of changed strings to our translator and he sees the changed, added and removed strings.
> OH, with gettext you can see where the text is placed, because it is
> autogenerated in comments inside the po(t) file. Like for example:
> #: Seaside-Gettext-Examples,WAGettextExample>>renderContentOn:
> msgid "fontsize"
> msgstr "" --> This is the translation key
This is not specific for gettext, but the format supports it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside