View previous topic :: View next topic |
Author |
Message |
lsw
Joined: 27 Jan 2012 Posts: 6
|
Posted: Fri Jan 27, 2012 10:39 am Post subject: Command Line |
|
|
We are trying to integrate globalizer into our build task.
After translators have edited the globalizer file, the changes should be transfered to the resx files. This works fine with the command line.
In the other direction, when a developer adds a new entry in a resx file, it should be added to the globalizer file. Until now we did this manually in Globalizer with the Scan function. But, I didn't find an option for the command line interface which would support that.
Did I overlook this option or is it just not supported? |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Fri Jan 27, 2012 11:32 pm Post subject: |
|
|
There is currently no command line option for scanning a workspace. This is because while you could scan a project automatically you would still have to translate the strings manually. _________________ Infralution Support |
|
Back to top |
|
|
lsw
Joined: 27 Jan 2012 Posts: 6
|
Posted: Mon Jan 30, 2012 9:01 am Post subject: |
|
|
Is there a chance that this option will be implemented in the near future?
It would be sufficient to insert dummy values (empty string, a unique number, ...).
In our case that would be useful, as the scanning of the workspace and the translation are done by 2 different persons (i.e. a developer and a translator (or once the integration in the build task works: the build server and a translator)). |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Mon Jan 30, 2012 9:33 pm Post subject: |
|
|
Its something we could look at. I'm not sure how it really helps you though - because exporting the translations to the translator will still be a manual process - so why not just scan before doing that? _________________ Infralution Support |
|
Back to top |
|
|
lsw
Joined: 27 Jan 2012 Posts: 6
|
Posted: Tue Jan 31, 2012 7:05 am Post subject: |
|
|
Because the translators are not software developers and don't really need/want the source code. They just get the binary of the application and the Globalizer (*.gxl) file.
So a developer has to perform the scan periodically, otherwise it can happen that the translators won't find a string in the Globalizer file, even though it appears in the binary, which has automatically been built by the build server.
So, if the Globalizer file would be automatically updated just before the build server compiles the source code, the Globalizer file would always be up to date. |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Thu Feb 23, 2012 5:50 am Post subject: |
|
|
Version 3.2.0 of Globalizer has just been released and incorporates a new /scan command line option that allows you to scan the workspace or selected targets and then saves the workspace. _________________ Infralution Support |
|
Back to top |
|
|
lsw
Joined: 27 Jan 2012 Posts: 6
|
Posted: Tue Feb 28, 2012 2:02 pm Post subject: |
|
|
Cool. Thank you. |
|
Back to top |
|
|
|