Hi Jody, It sounds similar to the NetBeans properties file editor which also shows translations side by side.
Michael On 22 September 2011 07:10, Jody Garnett <[email protected]> wrote: > If you guys like we have a stand alone tool for translators produced for > uDig; it allows people to download a zip of all the interesting files for > translating; shows the different translations side by side; and users can > zip up the result to attach to JIRA. > Details here: > - http://udig.refractions.net/confluence/display/ADMIN/Adding+Translations > -- > Jody Garnett > > On Wednesday, 21 September 2011 at 7:34 PM, Michael Bedward wrote: > > Thanks a lot Frank, that's a good summary to get us thinking. > > Perhaps you, Jody and myself (and anyone else interested of course) > could tee up a time for a chat about this on IRC soon. Sometime on the > weekend or early next week would be best for me. I'm in the same > timezone as Jody (GMT+10). > > Michael > > On 21 September 2011 17:38, Frank Gasdorf <[email protected]> > wrote: > > Hi folks, > Thanks Michael! > Yesterday I had a chance to play with and here are some points I'd like to > share: > pros: > * its possible to version files, means if a property file got once uploaded > it is possible to upload a newer one and the main file will be merge server > side. as a result you get added properties displayed as not translated (easy > workflow for translators, they do not have to care about added properties > anymore, in case the developer added these only in the main property file) > * there is an API for the service to get files up- and downloaded, which > could be integrated in the build process > * translators do not have to have commit access to the (SVN) source > repository, no developer skills required and the translators don't need to > know anything about project source structures (src/main/resources) > * translation support with google's and MS's translation services > * translation completion status -> everybody can see and feel free to > contribute (its quite hard for non developers to get involved because of > commit access registration procedure) > * translators can only change property files and do not have access to the > whole sources and therefore can not brake any feature and code > cons: > * In many projects the property files have the same name in different > modules, you can upload only files, not folder structures with property > files, therefore its required to have a temp. renaming process to get files > uploaded and a 2nd step to rename and copy the downloaded translations back > to the original folder structure. I started with a shell script to get all > the GeoServerApplication.properties from the web folder copied into one > folder, where the file can uploaded from: > > MY_EXPORT_DIR=../../properties > if [ ! -d "$MY_EXPORT_DIR" ]; then > mkdir $MY_EXPORT_DIR > fi > for i in $(find . -name "GeoServ*.properties") > do > echo $i > newstring="${i/\/src*esources\//_}" > newfile=${newstring:2} # remove "./" > #copy the file into the specified folder > cp $i ../../properties/$newfile > done > > * lack of synchronization, if a developer added or deleted properties to > keep the crowdin sources up to date, properly it would be possible to add > post commit hooks to repositories to synch *.properies files with crowdin > * synchronization back from crowdin to source repository sill requires > commit access. BUT who and when will the sources in repository be updated > * maintaining many branches/versions lead to as many projects in crowdin as > versions are maintained > Let the developers do there work and give all translators a handy tools to > do their job too without having to many obstacles to get a completed > translation > IMHO its worth to check it out, particularly its free for OS projects. Its a > chance to get completed translations for many different languages!! But > first we should think about and test it a bit. As well as we should share > some thoughts about a process. > Cheers, Frank > > 2011/9/21 Michael Bedward <[email protected]> > > Hi folks, > > Frank Gasdorf pointed me to Crowdin: a collaborative translation > service for software projects which offers free accounts for OS > projects. Franks has started a GeoServer project there. > > I've just setup a project for the swing module: > http://crowdin.net/project/geotools-gui. The "gui" tag is because I > hope that it might also be useful to gt-swt. I haven't done anything > other than upload the root properties files and apply to the Crowdin > admins for OS project status. > > Frank mentioned some shortcomings with the service (e.g. no ability to > sync to your source repository) but it still seems like it might be > useful, especially as the call for volunteers to help with swing > localization, via the blog and user list, has got the usual response > so far - none :) > > Michael > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
