-
Notifications
You must be signed in to change notification settings - Fork 991
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
[RFC] Translations and Internationalization #110
Comments
[We might want to use the wiki for RFCs] |
I think a PR creating a file like RFCs/i18n.md would be easier to track
comments and updates. This way the repo also contains the design decisions
once it's merged
…On 17 Aug 2017 7:50 pm, "Baptiste Darthenay" ***@***.***> wrote:
[*We might want to use the wiki <https://github.com/Keats/gutenberg/wiki>
for RFCs*]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#110 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAphoyIcFh4xVsabjK9JZsJAv1HN9IgZks5sZBrigaJpZM4O6Cdk>
.
|
By the way for the languages map, I see more something like default_language = "en"
[languages]
[languages.en]
title = "My blog"
description = "Hello world"
[languages.fr]
title = "Mon blog" Which means renaming |
Closing in favour of #111 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
This feature aims to make Gutenberg support multilingual sites
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Guide-level explanation
Overview
URLs
Configuration
language_code
is now understood as the default languagelanguages
is an array of language codes as key, and the name in that language as value:The order matters: it could be rendered in the language selector widget.
The default language has to appear in the array, but don’t have to be the first language (even it might be more intuitive to be).
Content
File organization
The content files have to have the same name for multiple languages.
The language is defined in the extension prefix:
{name}.{language_code}.{extension}
The language code can be omitted for the default language.
Slug
I18n
Context
lang
: the current language code, always available, even for default language;language
: the current language.language.code
is equivalent tolang
;config.languages
: used for building the language selector by iterating the key / value pairs;section.languages
listing the available translations for the current section;page.languages
listing the available translations for the current page;Misc
Language selector
RSS
Reference-level explanation
This is the technical portion of the RFC. Explain the design in sufficient detail that:
The section should return to the examples given in the previous section, and explain more fully how the detailed proposal makes those examples work.
Drawbacks
Why should we not do this?
Rationale and Alternatives
Unresolved questions
The text was updated successfully, but these errors were encountered: