You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wenn re-using a file that makes use of profiling in multiple guides, translating profiled sources is a problem - in the end there is multiple translated variants ofg the same file.
Locdrop should therefore package unprofiled sources by default. A switch ("--profiled-source ??) should allow to create profiled sources on demand.
Also requires an "upgraded" DEF file that contains all DC-files. Maybe this is a chance to enhance this functionality to make the DEF file an config where to specify arbitrary files that need to be added to the package.
The text was updated successfully, but these errors were encountered:
While doing the loc drop dry run with Tanja - I got to know, that all entities are resolved when handing over the files to translation - this also means, that all entity texts (e.g. SUSE Linux Enterprise Server etc.) go into the word count (in this example 4 words, each time the entity appears in text, multiplied by the languages...)
I strongly recommend to hand over the files without resolving the entities. This way we can also assure that product names or similar are not accidentally changed. We need to check with Vistatec first, why it was agreed that currently entities are resolved.
[Edit by sknorr: snipped one para from this for clarity]
Wenn re-using a file that makes use of profiling in multiple guides, translating profiled sources is a problem - in the end there is multiple translated variants ofg the same file.
Locdrop should therefore package unprofiled sources by default. A switch ("--profiled-source ??) should allow to create profiled sources on demand.
Also requires an "upgraded" DEF file that contains all DC-files. Maybe this is a chance to enhance this functionality to make the DEF file an config where to specify arbitrary files that need to be added to the package.
The text was updated successfully, but these errors were encountered: