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

Plone 6: Let sr language be Latin: Sprski. #334

Merged
merged 6 commits into from
Oct 17, 2021
Merged

Conversation

mauritsvanrees
Copy link
Member

The Plone 5 version of this PR is here: #327. That one makes Serbian available in its two character sets.

In Plone 6 we want to go one step further:

  • Default sr becomes Latin instead of Cyrillic. This is the most used of the two character sets.
  • Copied the Cyrillic translations to sr@Cyrl.
  • Renamed the Latin translations folder from sr_Latn to sr@Latn.

If you prefer the Cyrillic character set of this language, set this environment variable: zope_i18n_allowed_languages sr@Cyrl
If you prefer Latin already in Plone 5, you can set it to sr@Latn since Plone 5.2.6 (plone.i18n 4.0.7), provided the first mentioned plone.app.locales PR is merged and included.
See issue 326 <https://github.com/collective/plone.app.locales/issues/326>_.

@mauritsvanrees
Copy link
Member Author

This belongs together with plone/plone.i18n#39
I am testing the two together on Jenkins.

@mauritsvanrees
Copy link
Member Author

@erral If you could merge this and make a release, that would be great. I want to make a Plone 6 alpha the next few days.
If you are not sure this PR is good, I am happy with a release without it. We can include it later, if we agree on it.

@erral erral merged commit db2b52f into master Oct 17, 2021
@erral erral deleted the maurits/serbian-60 branch October 17, 2021 07:09
@erral
Copy link
Member

erral commented Oct 17, 2021

Merged and released version 6.0

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