Hi.
kleist wrote:
> So, Hanno and others...
>
> I've now spent two whole days with the Swedish
translation. Almost all
> tokens (except Kupu) are now more or less roughly
translated, and I've
> checked in all nine .po files. I'll be able to spend
more time with this the
> next week. Fellow Swedes: PLEASE REVIEW.
Hurray!!! Big kudos to you
> Please bear with me, if I've not yet grokked how this
procedure should be
> conducted. It's my debut as amateur translator.
If I sounded harsh in any way, please forgive me. I just
tried to give
you an explanation about the problem you encountered. If I
misunderstood
you again, please ignore me ;)
Questions are obviously always welcome And
especially from someone
new to the whole translation thing. We might fail to see
some problems,
as we are used to them for a long time now or don't realize
that some
important documentation is missing.
Hanno
> Hanno Schlichting-2 wrote:
>>
>>> I'm about to check in my first (very tentative)
additions/corrections to
>>> the
>>> Swedish translation of plone.pot. However, when
testing it I'm noting
>>> that
>>> several ui strings have no corresponding tokens
in my "plone-sv.po" (as
>>> in
>>> the 3.0 bundle in svn). For example, I have no
possibility to translate
>>> the
>>> word "History" on the last content
view tab.
>> Not all translations are in the plone-sv.po file.
We have eight more
>> *-sv.po files that all need to be translated in
order to get a fully
>> translated UI.
>>
>> The history tab for example is a feature that
originates from
>> CMFEditions and thus is found in
cmfeditions-sv.po.
>>
>> There are nevertheless still some UI strings not
found in any of the po
>> files. If you find one of these please first try to
find out if there is
>> already a ticket about it
>> (http://dev.plone.org/plone/query?st
atus=new&status=assigned&status=reopened&compone
nt=Internationalization&order=priority)
>> and otherwise open a new ticket (http://dev.plone.org/plon
e/).
>>
>> Most of the time missing strings are due to missing
i18n markup in the
>> source code itself, so patches fixing this are most
welcome. As I do the
>> extraction manually and not on every day, there
might be sometimes a
>> very small amount of strings already in the source
code, but not yet in
>> the translation files.
>>
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Plone-i18n mailing list
Plone-i18n lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n
a>
|