Skip to content

Conversation

@laanwj
Copy link
Member

@laanwj laanwj commented May 22, 2015

Document the effective use of translation strings for I18N. I finally found some time to write this down.
This is different from the translation process, in that it describes the use of translation strings in the source code, not the steps that have to be followed to push/pull them to Transifex.

Not intended to bike-shed, just some common-sense guidelines. But feel free to make suggestions.

@laanwj laanwj added the Docs label May 22, 2015
@laanwj laanwj force-pushed the 2015_05_translation_strings_policy branch 3 times, most recently from 0b66350 to c854a99 Compare May 23, 2015 08:13
@laanwj laanwj force-pushed the 2015_05_translation_strings_policy branch from c854a99 to 213f257 Compare May 23, 2015 09:30
@laanwj laanwj merged commit 213f257 into bitcoin:master May 27, 2015
laanwj added a commit that referenced this pull request May 27, 2015
213f257 doc: add translation strings policy (Wladimir J. van der Laan)
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant