Infralution Support

dsc · Joined: 20 Nov 2013 Posts: 3

Is there a way to call the /scan command line command with the "Scan All Cultures" option?

Infralution · Joined: 28 Feb 2005 Posts: 5027

No - this isn't something you would normally want to do (particularly from the command line). The "Scan All Cultures" option is usually only used as a mechanism for importing existing translations (which were added manually or using another tool). You don't really want to use it routinely because you should be generating translations from Globalizer using the build command. If you import existing translations using the "Scan All Cultures" option and the translations are not up to date (because you haven't done a build) then you run the risk of overwriting the translations in your Globalizer workspace with out of date translations.
_________________
Infralution Support

dsc · Joined: 20 Nov 2013 Posts: 3

Actually, I don't think we have this problem, because of the following:
In our workflow, when a translator is done with his translations (which he did using Globalizer), he runs a script which copies the new translations from the .gxl file back to the .resx files and then commits them to our SVN repository. This ensures that the .gxl file and the .resx files in our SVN repository both contain the same translations. So no translations made with Globalizer can get lost.

However, it doesn't work correctly the other way round: Sometimes, our developers add some translations directly to the .resx files. These translation will then not show up in the Globalizer file, because they are ignored by the /scan command, which is called in a script which creates the .gxl file from all the .resx files. So the translator needs to do these translations again. This could easily be avoided by calling /scan with the "Scan All Cultures" option.

So we would be very thankful to have /scan with "Scan All Cultures" available as a command line command.

Infralution · Joined: 28 Feb 2005 Posts: 5027

I'm still not sure that this is a good idea. My preference would be for the developers to use Globalizer to make any changes to translations and then rebuild. However we can add this option if you feel you really need it.
_________________
Infralution Support

dsc · Joined: 20 Nov 2013 Posts: 3

Infralution · Joined: 28 Feb 2005 Posts: 5027

Version 3.6.0 has now been released and includes an /allcultures option that allows you to scan non-invariant cultures from the command line.
_________________
Infralution Support