Infralution Support

[gunters63]

In the current version of Globalizer.NET (3.4.0.0) you can edit the comment field of translations.

But when you "Build Source Localization" to write back changes to the resx-Files the comment fields in the resx files don't get updated.

Also, when you then Scan again the comment fields in the Globalizer .gxl get overwritten again so any changes you made there get lost.

We have a large enterprise application here and want to use the content of the comment field to provide the translators with necessary context information and other stuff.

So for us it would be really nice if someone could add/change information to the comment field by using Globalizer only instead of using Visual Studio.

Regards,
Gunter

[Infralution]

Just to clarify currently if you write comments in the resx then when you scan they will replace the comments in Globalizer workspace. If you write comments in Globalizer (and there is no comment in the resx) then these are unaffected by scanning. So you should be able to add comments in Globalizer without problem - but if you change comments that were defined in the resx they will be overwritten when you scan.

The rationale behind this was that you would choose either to write comments in the resx files or else you write them in Globalizer. We didn't really anticipate wanting to edit comments from the resx and save them back - but this is certainly something we can have a look at.
_________________
Infralution Support

[gunters63]

Yes,

It is a large project (we bought five Pro licenses ) and we have an external translation team and non-developers responsible for organising the translation workflow.

Those persons regularily scan the sources for new strings to translate and adds comments aiding the translation team. They also collect the translations from the translation team (we use TMX import/export). Comments and translations are then written back to the sources.

The problem is, that also developers write an initial comment (we have special keywords targeted at an in-house written tool). So the comments we modify in Globalizer get lost at the next scan.

Probably you can make the "also write comments back" configurable.

Regards,
Gunter

[Infralution]

One possible issue with implementing this is that you would have select the Build invariant files option (otherwise the invariant resx files where the comments are won't get built). Normally however you don't want to use this option - unless you have scanned the project and made some corrections to invariant translations in Globalizer. If you use this option routinely without scanning first you run the risk of overwriting newer changed invariant entries with older entries from the Globalizer workspace. So you would need to take care using this.
_________________
Infralution Support

[gunters63]

That would be no problem for us, because even the english (invariant) texts will regularly get corrected by reviewers (internal user champions for example) because the developers often don't use the correct "corporate" technical terms or it isn't consistent with other texts.

Or in other words, even the "developer" english will get translated .

We will have to be careful if developers change their texts after the initial submit, that is true.

By the way: If you have a baseline active and someone changed strings in the resx and it also was changed in the .gxl: Does Globalizer warn in that case? It should be technical possible.

[Infralution]

[gunters63]