Hello Ko,
Our schedule has slipped by 1 week, so translators will have an extra
week to update translations.
I'll send an email about this shortly. (I've already updated the
schedule you have a URL to below).
So translations should be complete by 9 February 2015.
On 1/02/2015 12:47 am, Ko Nagase wrote:
Hi list,
Is OSGeo Live 8.5 translation deadline just February 2nd (next 48 hours) ?
https://docs.google.com/a/georepublic.de/spreadsheet/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&usp=drive_web#gid=0
By the way, I wrote that I will try to "gettext" tool (*.pot .etc) in
previous mail,
but, I didn't have much time to do that in these months...
So, about ver 8.5 Japanese translation, I am thinking to do it by current way.
Regards,
2014-12-10 18:16 GMT+09:00 Ko Nagase <[email protected]>:
Hi Cameron,
Thanks for answer.
2014-12-10 4:54 GMT+09:00 Cameron Shorter <[email protected]>:
The OSGeo-Live translation process is currently linked from:
http://wiki.osgeo.org/wiki/Live_GIS_Disc#Translate
While it seems to mostly work, I acknowledge that there is likely a better
way to do things, and if someone would like to step up and implement a
better process, then that would be great.
Okay.
I will try to think about it more, later.
Thanks,
On 9/12/2014 6:36 pm, Ko Nagase wrote:
Hi list,
I am not sure whether my question is related with separating version
number definition,
but is there some plan about "gettext" tool (*.pot .etc) based
translation workflow
like the following MapServer documentation development guide links ?
http://mapserver.org/el/development/documentation.html#the-old-way-for-translations
http://mapserver.org/el/development/documentation.html#the-standard-internationalization-system-i18n-for-translations
Regards,
2014-12-09 16:22 GMT+09:00 Astrid Emde <[email protected]>:
Hello Cameron,
thanks for your answer.
Maybe we could check conf.py for changes too and define a rule for
commit messages like - "version mapbender3 changed, final 8.5"
If something in the text of the overview files changes it still means
that the translators must have a look and translate.
I like your idea to loop through all translations and updates the
version number to the English master version.
Astrid
Am 05.12.2014 10:02, schrieb Cameron Shorter:
Hi Astrid,
You bring up a valid concern.
There is a reason that we currently prefer version numbers to be hard
coded into the Project Overview text instead of by using a variable.
We wish to verify that if an application has been updated, then
someone has assessed whether the Project Overview has been looked at
and updated. We do this by checking svn timestamps on the
<project>_overview.rst. If the version number changes, then the
<project>_overview.rst should change too. If the version number is
stored in a conf.py file instead, then we will need to think of
another way to check that each ProjectOverview has been reviewed and
updated.
I'm open to suggestions.
We could relatively easily write a script which loops through all
translations and updates the version number to the English master
version.
On 4/12/2014 5:50 pm, Astrid Emde wrote:
Hello,
I do not know, whether you discussed this before.
Before each OSGeo-Live version comes out the translators have to edit
many files and sometimes only have to change the version of the
software.
Things are much easier and less work, if the version is only defined at
one place as a variable and the version is used in all the overview
translations.
Some projects use this way already and I would like to encourage more
projects to make it this way.
Have a look at:
http://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/doc/conf.py
1.) f.e. define |version-geoserver| replace:: 2.5
2.) and refer in the xx_overview.rst like this
http://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/doc/de/overview/geoserver_overview.rst
**Software Version:** |version-geoserver|
Like this only changes in the text of the overview document have to be
translated for every new version.
Astrid
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Mit freundlichen Grüßen
Astrid Emde
GIS-Consultant
********************************************
Where2B Konferenz 2014
11. Dezember 2014 in Bonn
www.where2b-conference.com
********************************************
Astrid Emde
WhereGroup GmbH & Co.KG
Eifelstraße 7
53119 Bonn
Germany
Fon: +49(0)228 90 90 38 - 19
Fax: +49(0)228 90 90 38 - 11
[email protected]
www.wheregroup.com
Folgen Sie der WhereGroup auf twitter:
http://twitter.com/WhereGroup_com
Amtsgericht Bonn, HRA 6788
-------------------------------
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
-------------------------------
pgp-public key:
http://pgp.mit.edu:11371/pks/lookup?search=0x06DA52D72D515284
Signierte und/oder verschlüsselte Nachrichten sind sehr willkommen
Signed and/or encrypted mail is highly appreciated
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W www.lisasoft.com, F +61 2 9009 5099
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Ko Nagase (長瀬 興)
Georepublic Japan
mail: [email protected]
web: http://georepublic.co.jp
--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W www.lisasoft.com, F +61 2 9009 5099
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
