String Freeze and Call for Translations

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

String Freeze and Call for Translations

Ted Felix-2
   String freeze for 17.04 begins today.  This marks the beginning of
translation week.  Translators have until 4/18 to commit or post patches
for translations for 17.04.

   Rosegarden 17.04 will be released next Wednesday, 4/19.

Ted.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

D. Michael McIntyre-3


On 04/12/2017 07:23 AM, Ted Felix wrote:
>    String freeze for 17.04 begins today.  This marks the beginning of
> translation week.  Translators have until 4/18 to commit or post patches
> for translations for 17.04.
>
>    Rosegarden 17.04 will be released next Wednesday, 4/19.

I used to post the status report from scripts/make-ts along with these
announcements.  I used to run that immediately prior to declaring a
string freeze.

It's pretty likely that I will always have enough time to spare to get
around to this little bit of fiddling within 2-3 days.  I'm not actually
vanishing.  I've been stuck with the Spanish translation for years, and
I'll keep up with that too.  I'll let you know if I can't get it
finished before the deadline.

------------------------------------------------------------------------------
             TRANSLATION STATUS REPORT FOR THE ROSEGARDEN PROJECT
------------------------------------------------------------------------------

                    rosegarden.ts contains 4477 messages

Language   Total     Translated  Untranslated   Unfinished   Obsolete
Status
--------   -----     ----------  ------------   ----------   --------
-------
en         4478      23          4434           4            0
[%%%%-]
en_GB      4478      106         4349           4            0
[%%%%-]
en_US      4478      23          4433           4            0
[%%%%-]
es         4478      4424        5              4            9
[%%%%-]
fr         4478      4207        220            6            9
[%%%%-]
de         4477      4414        146            199          145
[%%%%-]
cs         4477      4278        284            202          145
[%%%%-]
it         4478      4154        396            341          131
[%%%%-]
sv         4478      4276        285            341          141
[%%%%-]
pt_BR      4477      4245        312            352          139
[%%%%-]
ja         4478      4203        358            412          140
[%%%%-]
pl         4477      4171        387            471          139
[%%%%-]
fi         4478      3923        635            557          137
[%%%%-]
zh_CN      4478      4012        552            718          132
[%%%%-]
ru         4478      3419        1058           1340         67
[%%%--]
nl         4479      2936        1554           1404         58
[%%%--]
id         4478      2201        2286           2414         42
[%%---]
ca         4478      2396        2078           4475         48
[-----]
cy         4478      1796        2693           4475         44
[-----]
et         4478      1866        2623           4475         33
[-----]
eu         4478      2471        2009           4475         52
[-----]

Total:        total strings that are not obsolete

Translated:   strings that have been translated

Untranslated: strings that have no translation (may be finished)

Unfinished:   strings that have not been marked as finished (may or
               may not have a translation)

Obsolete:     strings were translated, but these translations are no
               longer used in the source (frequently happens after
               someone edits a text to make a correction)

Report produced on Wed, 12 Apr 2017 18:34:45 -0400

--
D. Michael McIntyre

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

Ted Felix-2
On 04/12/2017 06:42 PM, D. Michael McIntyre wrote:
> I used to post the status report from scripts/make-ts along with these
> announcements.  I used to run that immediately prior to declaring a
> string freeze.

   OK, I'll add that to the process.

   One thing I noticed...  make-ts generates three files that are not in
version control:

   data/AutoloadStrings.cpp
   data/InstrumentStrings.cpp
   data/QMenuStrings.cpp

   These are generated temporarily to make sure strings from various
non-code places end up in the .ts files.  Since we don't ignore these in
version control, they are a nuisance and have to be deleted manually or
excluded when committing.

   Some solutions come to mind:

1. Go ahead and commit them.  The advantage to this is that they are
always available for translators to refer to, even if they don't run
make-ts.  It also makes it clear that these are to be in version control.

2. Add them to the svn:ignore property for the data directory.  This way
they won't be accidentally committed.  Translators can generate them any
time they want, and they won't show up when committing.  This is
probably the most gentle change.

3. Have the make-ts script delete them once it is done.  My problem with
this is that the files will no longer exist if someone runs make-ts and
starts doing translation work.  I assume that the translation tool will
then have nowhere to point them to for an explanation as to why these
strings are in the .ts file.

   Worst-case, we can just document the issue and move on.

   Any preference for any of these solutions from the perspective of a
translator?

Ted.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

D. Michael McIntyre-3
On 04/12/2017 07:55 PM, Ted Felix wrote:

>    One thing I noticed...  make-ts generates three files that are not in
> version control:

>    These are generated temporarily to make sure strings from various
> non-code places end up in the .ts files.  Since we don't ignore these in
> version control, they are a nuisance and have to be deleted manually or
> excluded when committing.

Why do they require special handling when committing?  They aren't under
version control, so Subversion ignores them.

$ echo garbage > data/AutoloadStrings.cpp
$ svn commit data
$ cat data/AutoloadStrings.cpp
garbage

I admit they're a weird hack, but I haven't paid these files any mind in
years.  I don't see this as a real problem.  Maybe it's a git thing?

> 1. Go ahead and commit them.  The advantage to this is that they are
> always available for translators to refer to, even if they don't run
> make-ts.  It also makes it clear that these are to be in version control.

What possible advantage is there to putting them under version control?

> 2. Add them to the svn:ignore property for the data directory.  This way
> they won't be accidentally committed.  Translators can generate them any
> time they want, and they won't show up when committing.  This is
> probably the most gentle change.

I don't see the harm, but translators never generate these files.  We
generate them as an intermediate step between editing, eg., the .rc
files and putting updated strings into the .ts files.

The only time translators look at code is when it's not clear what a
string means in context.

> 3. Have the make-ts script delete them once it is done.  My problem with
> this is that the files will no longer exist if someone runs make-ts and
> starts doing translation work.  I assume that the translation tool will
> then have nowhere to point them to for an explanation as to why these
> strings are in the .ts file.

In of itself, that probably isn't such a big concern.  These files don't
have any especially useful context information anyway.

>    Any preference for any of these solutions from the perspective of a
> translator?

Translator perspective:  Who cares?  Seriously, translators do not care
in the slightest what happens with these files.

I don't care either, beyond not breaking anything.  If it ain't broke,
what's there to fix?  That being said, if your OCD compels you to come
up with a different way of handling these (which I could well
understand, and am not mocking) then by all means do whatever you want
with them as long as you don't break nothin'.

--
D. Michael McIntyre

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

Ted Felix-2
On 04/13/2017 06:19 PM, D. Michael McIntyre wrote:
> Why do they require special handling when committing?  They aren't under
> version control, so Subversion ignores them.

   They pop up for me anyway when I do an svn status (or git status).
It would be nice to not see them.  To me it looks like I've screwed
something up.

   I'll go ahead and add them to svn:ignore to get them out of my way.

> That being said, if your OCD compels you to come
> up with a different way of handling these (which I could well
> understand, and am not mocking) then by all means do whatever you want
> with them as long as you don't break nothin'.

   Heh.  It's not OCD so much as it is my really weak memory.  That
requires removing distractions, like these files that pop up with svn
status.  And doing extensive documentation of everything.

   Ok, it's really OCD.

Ted.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

David Faure
In reply to this post by Ted Felix-2
On jeudi 13 avril 2017 01:55:00 CEST Ted Felix wrote:

>    Some solutions come to mind:
>
> 1. Go ahead and commit them.  The advantage to this is that they are
> always available for translators to refer to, even if they don't run
> make-ts.  It also makes it clear that these are to be in version control.
>
> 2. Add them to the svn:ignore property for the data directory.  This way
> they won't be accidentally committed.  Translators can generate them any
> time they want, and they won't show up when committing.  This is
> probably the most gentle change.
>
> 3. Have the make-ts script delete them once it is done.  My problem with
> this is that the files will no longer exist if someone runs make-ts and
> starts doing translation work.  I assume that the translation tool will
> then have nowhere to point them to for an explanation as to why these
> strings are in the .ts file.

4. Generate them in the build dir ;)

--
David Faure, [hidden email], http://www.davidfaure.fr
Working on KDE Frameworks 5


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
Reply | Threaded
Open this post in threaded view
|

Re: String Freeze and Call for Translations

Ted Felix-2
On 04/14/2017 03:11 AM, David Faure wrote:
> 4. Generate them in the build dir ;)

   Hmmm.  Yeah.  make-ts should be runnable from anywhere.  It's not
right now.  Then we can just run it in the build dir and problem solved.

   I assume we could also add a "make ts" target to the cmake system
that would run it for us.

Ted.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rosegarden-devel mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel