Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It would be awesome to include some translation files to the distribution (french, german and spanish for example).
English should be selected as default.
The idea would be to create a script that will check the current version of the .po files, download the latest version and commit them to the installation profile.
Comment | File | Size | Author |
---|---|---|---|
#14 | 1632550-13-installation-welcome.jpg | 608.67 KB | joshmiller |
#14 | 1632550-13-installation-welcome-v2.jpg | 611.74 KB | joshmiller |
#13 | 1632550-13-installation-welcome.jpg | 609.12 KB | joshmiller |
#13 | 1632550-13-installation-welcome-v2.jpg | 612.05 KB | joshmiller |
#11 | Magento Installation | 147.11 KB | joshmiller |
Comments
Comment #1
GuGuss CreditAttribution: GuGuss commentedSince Amitai is working on the multilingual, that could be a nice task ;)
Comment #2
amitaibuWe should probably also include http://drupal.org/project/l10n_update/
Comment #3
RoySegall CreditAttribution: RoySegall commentedTo enable translations in the install porcess, all we need to do is to put to .po files in folder called "translations" in the installation profile folder.
In my commit i put the German, French, Spanish and Hebrew translations. The files are not updated to 7.14 because i found 7.13, but no worry - the module "I10n update" can update the modules with the latest translations files.
We can also use this functionality for that in the install and i think this could be the next thing in this task.
Comment #4
bojanz CreditAttribution: bojanz commentedTo be honest, I really don't like this.
As soon as you add other languages, the text about "Installing Drupal in other languages" disappears and we're left with the screen shown in Roy's screenshot (http://drupal.org/files/Selection_031_0.png). This makes it look as if we're the ones doing and providing those translations, and not the community (leading to "Why isn't my language X in the list?").
Furthermore, since these are community translations, many things in Kickstart aren't translated (see my "mixed-languages" attached image), which doesn't look very professional.
Then I complete the install and am taken to an english "getting started'" with most of the frontpage and at least half of the menu being in english.
Those aren't the problems we can fix, and they make us look bad.
I vote for documenting this process in a user guide and recommending i10n_update, but leaving it at that.
Comment #5
RoySegall CreditAttribution: RoySegall commentedI agree - i think that all the related issues to i18n of commerce kickstart need to be a differential part rather then integral.
Comment #6
aleighs CreditAttribution: aleighs commentedI agree with bojanz but I understand the desire to show that other languages are at least possible, so here's a couple of different options.
1) We put a note on this page that alerts the user that they can translate the interface into other languages and we include a link to documentation
2) We include the unfinished po files, somehow gray out the languages as incomplete, and link to documentation on how to finish them.
Comment #7
RoySegall CreditAttribution: RoySegall commentedI din't wrote that the filed are unfinished - just not updated to the 7.14. The i10n update module can handle that. He can also download available translation files for all the modules.
Comment #8
bojanz CreditAttribution: bojanz commentedI'd go with this:
Attaching screenshots on how that looks right now. We can try and alter that text.
Comment #9
bojanz CreditAttribution: bojanz commentedOkay, so let's turn this into an actionable issue.
We want to hide the current "select language" screen completely.
We'll show a link leading to a docs page explaining the translation of Kickstart on the "select additional functionality" step, where the user will choose
whether he wants to translate the Kickstart UI at all (which will enable the required modules).
Since the language screen is the first screen of the install process, we need a new one. So showing some sort of "Welcome" text would fit nicely.
We need to figure out how that screen will look and what it will say first. The PHP part of the implementation is trivial.
Comment #10
joshmillerI will need to wrap my head around this a bit more, but will be using #1694546: Visual update of installation screen to mockup the screen.
Comment #11
joshmillerWelcome Installation Screen Research...
Comment #12
Bojhan CreditAttribution: Bojhan commentedI do advise having something useful there, nobody likes a page that is just there to sell you on something you are already installing anyway.
Comment #13
joshmillerBelow is my first attempt. I'm not sold on putting the language in a callout, just wanted to try it.
[EDIT: Typos... see next message...]
Comment #14
joshmillerOption 1:
Option 2:
Comment #15
bojanz CreditAttribution: bojanz commentedLet's go with option number two, the first paragraph only (without the "Drupal has many...") paragraph.
Comment #16
bojanz CreditAttribution: bojanz commentedMarking as a beta blocker. It's a fairly simple change, and I feel that beta should be as close as possible to the final release, UI-wise.
Comment #17
HazaImplemented there https://code.drupalcommerce.org/283
Comment #18
bojanz CreditAttribution: bojanz commentedTweaked and merged.