Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n improvements #5

Merged
merged 2 commits into from
Jul 14, 2014
Merged

i18n improvements #5

merged 2 commits into from
Jul 14, 2014

Conversation

glueckpress
Copy link
Contributor

(Notes from this commit:)

Several suggestions for improved use of formatting functions, context and notices for translators. For reference see http://wceu2013.ottopress.com/ (once it’s back in place).

Key points:

  1. Deliver complete messages. Splitting text strings in translatable substrings bears the premise those chunks could be used in other languages as they can in English. They often cannot.
  2. Use formatting functions mainly to keep HTML out of translatable strings. Security and all. _s needs to work on that, too, in places.
  3. Use Codestyling Localization to verify translatability of your code and language files. It supports context functions as well as translators notices and will notify you in case multiple textdomains can be found in your code (my-simone, twentyfourteen etc). Also nb.po does not seem to be a valid language file name. It probably should be nb_NO.po, accompanied by a
    .mo file.

Neat theme otherwise! Will provide German translation once this pull request has been accepted.

Several suggestions for improved use of formatting functions, context
and notices for translators. For reference see
http://wceu2013.ottopress.com/ (once it’s back in place).

Key points:

1. **Deliver complete messages.** Splitting text strings in
translatable substrings bears the premise those chunks could be used in
other languages as they can in English. They often cannot.
2. **Use formatting functions mainly to keep HTML out of translatable
strings.** Security and all. _s needs to work on that, too, in places.
3. **Use [Codestyling
Localization](https://wordpress.org/plugins/codestyling-localization/)
to verify translatability of your code and language files.** It
supports context functions as well as translators notices and will
notify you in case multiple textdomains can be found in your code
(my-simone, twentyfourteen etc). Also nb.po does not seem to be a valid
language file name. It probably should be nb_NO.po, accompanied by a
.mo file.

Neat theme otherwise! Will provide German translation once this pull
request has been accepted.
mor10 added a commit that referenced this pull request Jul 14, 2014
i18n improvements courtesy of @glueckpress. Merged without alterations.
@mor10 mor10 merged commit d59487b into mor10:master Jul 14, 2014
@glueckpress glueckpress deleted the i18n-improvements branch July 14, 2014 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants