This is a meta-meta issue to help you navigate the maze of Drupal 8 Multilingual Initiative issues with their relations. Go to these main topic areas to participate in different parts of the initiative. You can find news, IRC meeting information and other details on the Drupal initiatives group at http://groups.drupal.org/drupal-initiatives (check out the initiative dashboard).
Map of the main issues
Read the notes on the root mindmap node (hover over note icon) for information on what different markers mean.
Status update / roadmap video
Check out this video to understand the components, status and roadmap for the Drupal 8 Multilingual Initiative:
Drupal 7 modules vs. Drupal 8 modules/functionality plan
Sub-issues
#1260488: META: Introduce real language APIs
#1269834: META: Clean up language negotiation code
#1260658: META: better t()-related APIs in locale module
#1260628: META: Better translation management API in locale module
#1191488: META: Integrate l10n_update functionality in core
#1269842: META: Improve language support on entities and fields
#1260690: META: Improve multilingual user experience in Drupal 8
Comment | File | Size | Author |
---|---|---|---|
#6 | D8MIV2Video.png | 66.64 KB | Gábor Hojtsy |
Comments
Comment #1
plachComment #1.0
plachAdd locale API sub-issue and field DX sub-issue
Comment #1.1
Gábor HojtsyAdd t() related issues
Comment #1.2
Gábor HojtsyStructure a bit
Comment #2
sunComment #3
jherencia CreditAttribution: jherencia commentedSub.
Comment #4
podaroksubscribe
Comment #4.0
podarokAdded UX issue
Comment #4.1
Gábor HojtsyAdd negotiation related cleanup META issue
Comment #5
Gábor HojtsyAdded new meta issues for #1269834: META: Clean up language negotiation code and #1269842: META: Improve language support on entities and fields.
Comment #6
Gábor Hojtsy(Attachment for update video.)
Comment #6.0
Gábor HojtsyAdd more generic Entity level issue
Comment #6.1
Gábor HojtsyAdd update video
Comment #7
webchickSubscribe.
Comment #7.0
webchickTurn to full HTML
Comment #8
sylvain_a CreditAttribution: sylvain_a commentedSuscribing.
Comment #9
dasjoComment #10
renat CreditAttribution: renat commentedSub
Comment #11
reglogge CreditAttribution: reglogge commentedsub
Comment #12
danoguru CreditAttribution: danoguru commentedI think it would be a good idea if translation strings would have their own IDs, because one word in English could have many meanings and in a different language this can be different words.
Comment #13
Gábor HojtsyCurrent focus issues (all to simplify / unify language setup and configuration):
#1266318: Make English a first class language
#1280530: Decouple domain/path negotiation setup from language configuration
#1260860: Rework language list admin user interface
Comment #13.0
Gábor HojtsyAdd docs issue
Comment #13.1
Gábor HojtsyAdd map of issues
Comment #14
Bojhan CreditAttribution: Bojhan commentedCan you make the mindmap available per PDF?
Comment #15
Gábor Hojtsy@Bojhan: the idea is that the mindmap would be continually updated to reflect current status and breakdown of tasks. You can export a PDF of the tasks anytime via the export feature of the tool which can be access in full screen view (once you hit full screen on the embed, look for the box with an arrow: https://skitch.com/gabor.hojtsy/f9ide/drupal-8-multilingual-initiative-d...).
Comment #16
Gábor HojtsyCurrent focus, reviews welcome on #1301148: Stop pretending we have configuration translation for languages and #1301460: Decouple domain/path language negotiation storage from language config storage so we can move on with breaking out language functionality from locale module at #1301040: Move language listing functionality from locale.module to a new language.module. Please help there. Thanks!
Comment #16.0
Hanno CreditAttribution: Hanno commentedUpdated issue summary.
Comment #17
Hanno CreditAttribution: Hanno commentedFor accessibility we also need the further implementation of 'language of parts', to present the language as attribute for text parts in another language. (http://groups.drupal.org/node/145894). Probably make it a meta-issue or include this in the roadmap?
Here are some relevant issues:
#1165476: if t() string has no translation or fallback language, text should have lang attribute
#1164926: Nodes need to have languages specified separately for accessibility
#1165806: language of parts
#1164682: links with a known language need language identifier
#986156: Node teasers should add 'lang' tag if its language differs from the page language
and for WYSIWYG in core: #1165466: Language of parts, accessibility and multilanguage: language button
EDIT: an issue created for this: #1323338: [meta] Conform to WCAG Success Criterion 3.1.2: Language of Parts
Comment #18
tinker CreditAttribution: tinker commentedSorry for the semi thread jacking. Tried looking for a drupal 8 dev roadmap but could not find one and this looked like the most relevant place to ask. Are there any plans to have the locale module be the central repository of locale information? I'm referring to information referenced by country such as:
If there are plans could someone point me towards info?
If no plans is anyone up for discussion or could provide input to aid development effort?
I think this would need some implementation in core which could be built upon by modules to meet user feature requirements. e.g. units are not part of core, only enabled when needed, and provide unit conversion based on users country code provided by core. Could also be used by installer to simplify default site settings. e.g. user confirms their country that was possibly detected from browser at which point installer loads country profile that has default settings for timezone, date format, languages etc.
I came across Unicode Common Locale Data Repository (CLDR) which seems to have all the info freely available see http://cldr.unicode.org/
Thanks for any input.
Comment #19
Gábor Hojtsy@tinker: we don't currently plan to have that, the date formats in Drupal 7 for example tie to the language list (built in in Drupal core). We are concentrating on fixing functionality gaps in content and especially config translation. We will clear out the locale namespace to be used for real locale functionality eventually, but it is not currently in the plans for Drupal 8. However, that does not mean that any such work would be refused if we can make it fit in somehow with the other changes. What do you think?
Comment #20
plachPersonally I'd like to see us intoduce at least the very minimum needed to implement a full solution in contrib, which could be incorporated in D9 after having the time to mature during the D8 lifecycle.
Comment #21
Gábor Hojtsy@plach/@tinker: want to open an issue about this to discuss so we don't spam the subscribers here?
Comment #22
Hanno CreditAttribution: Hanno commentedWould be a great initiative to introduce localisation for other data than language but can imagine this is something out of scope for D8MI. Having a centralised system for localisation information for contrib modules might make sense (standard.inc?). Some issues that could be tackled on the way:
#1178342: Allow contributed modules to alter the format_date() function result.
#52153: Add Number::format with settings to configure decimal point and thousands separators
Yes, would be great to have a meta-issue on this.
Comment #23
Mac_Weber CreditAttribution: Mac_Weber commented@Hannno: right now, in D7 it is possible to localize images, for example. If you use Entity Translations module.
I also think it is a very important feature to localize different fields and choose which fields can be localized.
I see many uses for these features in international websites.
Comment #24
Gábor Hojtsy@Mac_Weber: that is not related to the above discussion and there is no plan to remove translation support for fields.
Comment #25
tinker CreditAttribution: tinker commentedThanks for the info. I have started a issue as suggested and welcome more discussion in #1345758: META: Provide locale (regional) formats framework for automated translation of non textual data
Comment #26
Mac_Weber CreditAttribution: Mac_Weber commented@Gábor Hojtsy What do you think about including a link on this topic to a landing page with the schedule of IRC meetings, and more information about the initiative? I guess many people who find this discussion don't know about the IRC channel and other things going on.
Comment #26.0
Mac_Weber CreditAttribution: Mac_Weber commentedadd in image for modules plan
Comment #27
Gábor Hojtsy@Mac_Weber: added this to the top: You can find news, IRC meeting information and other details on the Drupal initiatives group at http://groups.drupal.org/drupal-initiatives (check out the initiative dashboard).
Comment #28
awm CreditAttribution: awm commentedsub
Comment #29
Gábor HojtsyGreat news! #1301040: Move language listing functionality from locale.module to a new language.module was comitted right before the holidays, so we have a language.module now in Drupal 8. To continue cleaning up the related language code, the following issues are currently in focus:
- #1387608: Unify language_list() and locale_language_list() - gets rid of a duplicated API function in locale.module in favor of the more general global function
- #1387586: Rename drupal_multilingual() to language_multilingual() - moves drupal_multilingual() to the language_* namespace for better DX
- #1357918: Missing update for language_default in language langcode update - continues converting to "langcode" for language codes in language module/objects
- #1357912: Convert path language code schema to langcode - continues converting to "langcode" in the path module and associated API functions
- #1280538: Language negotiation UX: default the path prefix setting on installation so that it actually works right away - improves the initial usability of negotiation configuration with saner defaults for new installs
Please help with these issues! Thanks!
Comment #30
Gábor HojtsyReviews would be very welcome still on these issues, all have supposedly ready and test-passing patches so all are waiting on human confirmation. Those are all my patches so I cannot actually help with pushing them forward:
- #1387608: Unify language_list() and locale_language_list() - gets rid of a duplicated API function in locale.module in favor of the more general global function
- #1357918: Missing update for language_default in language langcode update - continues converting to "langcode" for language codes in language module/objects
- #1357912: Convert path language code schema to langcode - continues converting to "langcode" in the path module and associated API functions
Review help needed once @fastangel comes back with code fixing the concerns that came up so far:
- #1280538: Language negotiation UX: default the path prefix setting on installation so that it actually works right away - improves the initial usability of negotiation configuration with saner defaults for new installs
Please help with these issues! Thanks!
Comment #32
Gábor HojtsyWith almost all of those issues landed, our current focus in terms of actionable is now the following:
- Even though the original patch in #1357918: Missing update for language_default in language langcode update landed, @sun found that language_default was not updated. That still needs more work in that department. This needs some serious help from people experienced with tests. I'm sort of stuck in there.
- Moving forward with the langcode update now for comments at #1410096: Convert comment language code schema to langcode. @fastangel could use some reviewers and guidance for upgrade path testing.
- In the spirit of making node and path work with language module only to deliver the promise of language.module much better there are two issues in #1414314: Make node and path depend on language module only for language support, get rid of locale_language_name and #540294: Move node language settings from Locale to Node module. Both issues need review and help.
- Finally, in preparation of migrating negotiations to language.module (or as part of that), we need to continue cleaning up that part of the API. That is at #1222106: Unify language negotiation APIs, declutter terminology.
Help in these areas is very welcome! Thanks in advance.
(Updated fixing link to #1414314: Make node and path depend on language module only for language support, get rid of locale_language_name).
Comment #33
Gábor HojtsyMove to new D8MI-meta tag to differentiate from concrete issues.
Comment #33.0
Gábor HojtsyAdd link to initiatves dashboard.
Comment #33.1
Gábor Hojtsylink to new hub
Comment #34
Gábor HojtsyDeprecating this with reference to http://groups.drupal.org/node/205628
Comment #34.0
Gábor HojtsyUpdated issue summary.