On Thu, Apr 18, 2013 at 7:56 AM, <svn_grass@osgeo.org> wrote:
Author: hamish
Date: 2013-04-17 22:56:53 -0700 (Wed, 17 Apr 2013)
New Revision: 55864
Modified:
...
grass/branches/releasebranch_6_4/scripts/v.db.join/v.db.join
...
grass/branches/releasebranch_6_4/scripts/v.db.update/v.db.update
...
Log:
clean up language (#1591 , partial merge of r55862 from trunk)
...
Modified: grass/branches/releasebranch_6_4/scripts/v.db.join/v.db.join
--- grass/branches/releasebranch_6_4/scripts/v.db.join/v.db.join 2013-04-18 05:50:21 UTC (rev 55863)
+++ grass/branches/releasebranch_6_4/scripts/v.db.join/v.db.join 2013-04-18 05:56:53 UTC (rev 55864)
@@ -14,7 +14,7 @@
#############################################################################
#%Module
-#% description: Allows to join a table to a vector map table.
+#% description: Joins a database table to a vector map table.
--> please don't break the translations if not really needed!
...
Modified: grass/branches/releasebranch_6_4/scripts/v.db.update/v.db.update
--- grass/branches/releasebranch_6_4/scripts/v.db.update/v.db.update 2013-04-18 05:50:21 UTC (rev 55863)
+++ grass/branches/releasebranch_6_4/scripts/v.db.update/v.db.update 2013-04-18 05:56:53 UTC (rev 55864)
@@ -15,7 +15,7 @@
#############################################################################
#%Module
-#% description: Allows to update a column in the attribute table connected to a vector map.
+#% description: Updates a column in the attribute table connected to a vector map.
--> same here. Now for up to 16 languages the strings must be remerged into
the .po files, translated and updated in SVN...
Markus
Hamish
April 18, 2013, 7:41am
2
Hamish:
> -#% description: Allows to join a table to a vector map table.
> +#% description: Joins a database table to a vector map table.
MarkusN wrote:
--> please don't break the translations if not really needed!
it's bad English to leave out the pronoun, also it was written
a bit too much in the passive voice; both should be fixed.
--> same here. Now for up to 16 languages the strings
must be remerged into the .po files, translated and updated
in SVN...
I note the cost, but in this case should not stop us fixing
text where it should be fixed.
is the i18n maintenance something that could be scripted to
make it be less work?
best,
Hamish
On Thu, Apr 18, 2013 at 9:41 AM, Hamish <hamish_b@yahoo.com> wrote:
is the i18n maintenance something that could be scripted to
make it be less work?
If you have a cmd line software to translate messages, yes
The rest is already scripted except for the human work to
actually translate to PL, DE, IT, JA, etc.
Markus
Hamish
April 18, 2013, 2:07pm
4
Hamish:
> is the i18n maintenance something that could be scripted to
> make it be less work?
MarkusN:
If you have a cmd line software to translate messages, yes
The rest is already scripted except for the human work to
actually translate to PL, DE, IT, JA, etc.
You really shouldn't dangle these little interesting challenges
in front of me, I'm supposed to be getting some sleep here.
Looking into it, ./locale/ is ~100MB, perhaps 25% of that is
English msgid chars to be translated (complete wild guess).
Google charges US$20 per million chars translated per lang.
(multibyte chars count as "1")
so 25mb*$20 ~ US$500 to run everything through their API -> "fuzzy".
no discounts for non-profits at this time.
https://developers.google.com/translate/v2/faq
https://developers.google.com/translate/v2/terms
https://developers.google.com/translate/v2/pricing
see also previous idea/prototype for automatic-man page
translation from the 6.3 days:
http://grasswiki.osgeo.org/wiki/Updating_GRASS_Documentation#Translations
(Babelfish is dead, but the Google demo still works)
Hamish