Open
Conversation
Specifying the resx-template option, along with the -g resx generator, allows to create files, from translated .po's for aspx consumption. Let's say you have a login.aspx.resx file used by asp.NET globalization. You first prepare a .pot as translation template: > vernacular -i login.apsx.resx -g po --pot -o login.pot At some point in time later, you get a fully translated login page in, say, French, named fr.po. If we convert it at this point back into a resx, we'll have vernacular generated ids, unsuitable for asp.NET. But we can use our original file as template, to generate the right ids: > vernacular -i fr.po --resx-template login.aspx.resx -g resx -o fr.aspx.resx That's it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specifying the resx-template option, along with the -g resx generator,
allows to create files, from translated .po's for aspx consumption.
Let's say you have a login.aspx.resx file used by asp.NET globalization.
You first prepare a .pot as translation template:
At some point in time later, you get a fully translated login page in,
say, French, named fr.po. If we convert it at this point back into a resx,
we'll have vernacular generated ids, unsuitable for asp.NET. But we can
use our original file as template, to generate the right ids:
That's it.