Re: [Localization] [ANNOUNCE] 0.94 schedule update: still on track
On 09/13/2011 11:03 PM, Markus Schlager wrote:
Hi Simon,
Thanks Markus for the feedback,
On Thu, 8 Sep 2011, Simon Schampijer wrote:
There have been one interesting string change in the last week: there
are two entries in the sugar.po that translate the same string
('Remove') but where the context is different. This has been marked
now using pgettext. Chris has pulled that change to Pootle and all
langs sugar.po have been refreshed. An example can be seen at [3][4].
Please give feedback if that addition was helpful to do a better
translation or if anything can be improved.
Context-information is great for translation. In this example, 'volume'
as hint was not particularly helpful to me, since this has at least two
very different meanings in German. 'clipboard' on the other hand was
clear anyway since the source-hint says something about clipboard-menu.
Maybe the text should be more verbose. How about: 'remove item from
clipboard' and 'eject the external device'
One type of content-information I'd appreciate a lot would be about the
function/type of text this is: Is it e.g. a button lable, a menu entry,
a help text, ...
How would that be done, as well with msgctxt using pgettext? Or are
there other ways? In general that would be a bigger effort and would
need to define a few guidelines for that but can be done of course if
the translator community thinks this would help a lot.
Regards,
Simon
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [Localization] [ANNOUNCE] 0.94 schedule update: still on track
On Thu, Sep 15, 2011 at 2:30 AM, Simon Schampijer si...@schampijer.de wrote:
On 09/13/2011 11:03 PM, Markus Schlager wrote:
Hi Simon,
Thanks Markus for the feedback,
On Thu, 8 Sep 2011, Simon Schampijer wrote:
There have been one interesting string change in the last week: there
are two entries in the sugar.po that translate the same string
('Remove') but where the context is different. This has been marked
now using pgettext. Chris has pulled that change to Pootle and all
langs sugar.po have been refreshed. An example can be seen at [3][4].
Please give feedback if that addition was helpful to do a better
translation or if anything can be improved.
Context-information is great for translation. In this example, 'volume'
as hint was not particularly helpful to me, since this has at least two
very different meanings in German. 'clipboard' on the other hand was
clear anyway since the source-hint says something about clipboard-menu.
Maybe the text should be more verbose. How about: 'remove item from
clipboard' and 'eject the external device'
One type of content-information I'd appreciate a lot would be about the
function/type of text this is: Is it e.g. a button lable, a menu entry,
a help text, ...
How would that be done, as well with msgctxt using pgettext? Or are there
other ways? In general that would be a bigger effort and would need to
define a few guidelines for that but can be done of course if the translator
community thinks this would help a lot.
Simon,
Developer's comments can be inserted in the code itself and are
extracted by gettext and displayed in the PO file in a manner that
does not disrupt translation.
# TRANS: Developer comment
in the code ends up in PO file as
#. Developer comment
and is displayed prominently.
Live examples of this can be seen in TamTam Suite (as one example)
where we've inserted extensive developer's comments (including wiki
links) describing the instruments tooltips. More specific reference
to lines in git can be given if needed.
cjl
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Localization] [ANNOUNCE] 0.94 schedule update: still on track
Hi Simon,
On Thu, 8 Sep 2011, Simon Schampijer wrote:
There have been one interesting string change in the last week: there are two
entries in the sugar.po that translate the same string ('Remove') but where
the context is different. This has been marked now using pgettext. Chris has
pulled that change to Pootle and all langs sugar.po have been refreshed. An
example can be seen at [3][4]. Please give feedback if that addition was
helpful to do a better translation or if anything can be improved.
Context-information is great for translation. In this example, 'volume' as
hint was not particularly helpful to me, since this has at least two
very different meanings in German. 'clipboard' on the other hand was clear
anyway since the source-hint says something about clipboard-menu.
One type of content-information I'd appreciate a lot would be about the
function/type of text this is: Is it e.g. a button lable, a menu entry, a
help text, ...
This type of information I consider very helpfull in order to get
consistent localizations.
Markus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
[ANNOUNCE] 0.94 schedule update: still on track
Hi,
we are still on track in our 0.94 development cycle [1]. The release is
three weeks away from now, we plan to release the 28th of September!
We have been entering string freeze now, which means: No string changes
may be made without confirmation from the localization team and
notification to the release team [2]. This freeze is meant to help the
translators finish their work and to not provide them with a moving
target. Now is the time we will see a lot of commits from our great
translators community, Activity developers please watch out for those
and do make releases to make that work available.
There have been one interesting string change in the last week: there
are two entries in the sugar.po that translate the same string
('Remove') but where the context is different. This has been marked now
using pgettext. Chris has pulled that change to Pootle and all langs
sugar.po have been refreshed. An example can be seen at [3][4]. Please
give feedback if that addition was helpful to do a better translation or
if anything can be improved.
Manuel is currently working on polishing up the tabbing experience in
Browse. There is one string change and a significant UI change [5]. Both
need to be discussed following the exception process [6].
So what's left to be done besides translating?
Right, bug fixing and testing!
I have been listing Features and changes on the pre-release-notes [7]
which should give a good sense of the bigger changes that needs testing.
General functionality testing like (networking, saving etc) are of
course welcome. I will add a list as well of the bugs we fixed so
potential regressions in those areas can be identified. Watch out for
more details here. There are instructions on the page as well how to
test and where to file bugs.
Three more weeks to go, let's make this a rock-solid, innovative and
fun-to-use release.
Regards,
Simon
[1] http://wiki.sugarlabs.org/go/0.94/Roadmap#Schedule
[2] http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
[3] Remove - clipboard
http://translate.sugarlabs.org/es/glucose/sugar.po?item=247view_mode=translate
[4] Remove - volume
http://translate.sugarlabs.org/es/glucose/sugar.po?item=369view_mode=translate
[5]
http://lists.sugarlabs.org/archive/sugar-devel/2011-September/033229.html
[6] http://wiki.sugarlabs.org/go/Development_Team/Release#UI_Freeze and
http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
[7] http://wiki.sugarlabs.org/go/0.94/Notes
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [ANNOUNCE] 0.94 schedule update: still on track
Just to emphasize that a string freeze is the signal for localizers
to really shift into high gear and complete the current Glucose and
Fructose string sets and for language admins to review and commit
those PO files.
If watching PO file commits roll in is your idea of a good time (I
know it gives me a thrill), please feel free to keep an eye on our new
piece of tracking infrastructure which catches all Sugar Labs and
eToys PO file commits. There is a slim chance that one or two Honey
actviities still hosted at dev.laptop.org might not be reported (maybe
WatchListen), but the overwhelming majority of Pootle commits to
Sugar projects will now be reported and archived on the list below:
http://lists.sugarlabs.org/archive/pootle-commits/\
Localizers, start your engines. Developers, put on your localizer hat
for a few days. If you don't have a second language (computer
languages don't count), recruit a friend who does.
cjl
On Thu, Sep 8, 2011 at 2:54 AM, Simon Schampijer si...@schampijer.de wrote:
Hi,
we are still on track in our 0.94 development cycle [1]. The release is
three weeks away from now, we plan to release the 28th of September!
We have been entering string freeze now, which means: No string changes may
be made without confirmation from the localization team and notification to
the release team [2]. This freeze is meant to help the translators finish
their work and to not provide them with a moving target. Now is the time we
will see a lot of commits from our great translators community, Activity
developers please watch out for those and do make releases to make that work
available.
There have been one interesting string change in the last week: there are
two entries in the sugar.po that translate the same string ('Remove') but
where the context is different. This has been marked now using pgettext.
Chris has pulled that change to Pootle and all langs sugar.po have been
refreshed. An example can be seen at [3][4]. Please give feedback if that
addition was helpful to do a better translation or if anything can be
improved.
Manuel is currently working on polishing up the tabbing experience in
Browse. There is one string change and a significant UI change [5]. Both
need to be discussed following the exception process [6].
So what's left to be done besides translating?
Right, bug fixing and testing!
I have been listing Features and changes on the pre-release-notes [7] which
should give a good sense of the bigger changes that needs testing. General
functionality testing like (networking, saving etc) are of course welcome. I
will add a list as well of the bugs we fixed so potential regressions in
those areas can be identified. Watch out for more details here. There are
instructions on the page as well how to test and where to file bugs.
Three more weeks to go, let's make this a rock-solid, innovative and
fun-to-use release.
Regards,
Simon
[1] http://wiki.sugarlabs.org/go/0.94/Roadmap#Schedule
[2] http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
[3] Remove - clipboard
http://translate.sugarlabs.org/es/glucose/sugar.po?item=247view_mode=translate
[4] Remove - volume
http://translate.sugarlabs.org/es/glucose/sugar.po?item=369view_mode=translate
[5]
http://lists.sugarlabs.org/archive/sugar-devel/2011-September/033229.html
[6] http://wiki.sugarlabs.org/go/Development_Team/Release#UI_Freeze and
http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
[7] http://wiki.sugarlabs.org/go/0.94/Notes
___
Sugar-devel mailing list
sugar-de...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [ANNOUNCE] 0.94 schedule update: still on track
Unmangled link http://lists.sugarlabs.org/archive/pootle-commits/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
