[META] Improve internationalization in 1.x

[herbdool]

There are a number of improvements we can make in 1.x that are backwards compatible (items in bold are prioritised):

• Make menu items translatable in core #225 | Make menu items translatable in core
• [CMI] Add config translation #704 | [CMI] Add config translation
• [D8] Add Transliteration to Core #904 | Add Transliteration in core
• Multi language site: Changing the front page for the English language changes the other languages front page too. #1638 | Changing the front page for the English language changes the other languages front page too.
• Transliteration doesn't respect site default language #2637 | Transliteration doesn't respect site default language
• Translate taxonomy terms #2934 | Translate taxonomy terms
• Identify translatable strings in core static config files #3455 | Identify translatable strings in core static config files
• Extend the translation module to include a block that can hold translated content. #3464 | Extend the translation module to include a block that can hold translated content.
• [Views] [multilingual] Titles of views in blocks cannot be translated #3498 | [Views][multilingual] Titles of views in blocks cannot be translated
• Front page to be configurable by language #3500 | Front page to be configurable by language
• Assign translatable config for Content types, Fields, Layouts and Image Styles #3515 | Assign translatable config for Content types, Fields, Layouts and Image Styles
• Allow default/required settings on multilingual ("Language") fields #4322 | Allow default/required settings on multilingual ("Language") fields

Misc:

• Localization server roadmap: [Meta] Roadmap backdrop-ops/localize.backdropcms.org#5
• Extract translatable config strings: Extract translatable config strings backdrop-contrib/potx#9
• [D8][UX] Rename the "Locale" module to "Interface Translation" #4562 [D8][UX] Rename the "Locale" module to "Interface Translation"

[docwilmot]

@herbdool I wonder if this should be more about the total i18n experience in Backdropland rather than just core. Should we be making an effort to ensure that all the needed bits are available? At the very least that might give us a broader view of what might be lacking.

So, the translation files, the localization server, contrib modules etc?

[herbdool]

@docwilmot perhaps that could be a meta to this meta. I was thinking first of focusing on core and 1.x but I'm flexible. We also have "projects" in github which are pretty useful for tracking the progress on issues so this could be multiple issues as part of a Internationalization project.

[olafgrabienski]

I like to focus on core / 1.x in this issue. Doing so, I expect to also get an image of the (hopefully few) tasks that need to be done in contrib and infrastructure.

Some issues are even connected, take for instance the Backdrop localization server: At the moment, during a Backdrop installation in a language other than English, people get a link to the Drupal localization server. If we want to improve the installation experience, we have to have our own localization server, so it's (also) a core issue.

[docwilmot]

@olafgrabienski thats my point. we should add the server issues to this META, because it is a 'core' issue then.

[olafgrabienski]

@herbdool I've added one issue to the description:

• Transliteration doesn't respect site default language Transliteration doesn't respect site default language #2637

There are two PRs for the issue but it's still unclear what's the best way to proceed. Would be great if you could have a look at it and give some feedback!