1- I think we could take as example some Linux distros. So the questions would go as...<br><br>a- Choose your default installation language - (Or it could be some icon or logo defining "speaking" with "?") Bases on the .po found.
<br><br>b-(Now in the default language) - Choose all language that you want installed : That would be all .po files found with a checkmark if they want to install it.<br><br>2- Sounds good.<br><br>4 and 5 - Could a rollback or history versoning could be interesting? Subversion style? (but a lot of work I guess).
<br><br>When the user would make an update, of the language pack or of a module, the system would ask :<br>- There are some changes in the language file. Would you like to apply the changed? (All changes are kept, so you can come back) [Apply all changes check]-[no changes]
<br><br>[check?] change 1 BEFORE1 AFTER1 ...<br>[check?] change 2 BEFORE2 AFTER2 ...<br>...<br><br>And if someone would go in the locale module, and search for the BEFORE1 string, they could found all versions.<br><br>These are just idears ;)
<br><br><br><br><br><div><span class="gmail_quote">On 9/2/06, <b class="gmail_sendername">Gabor Hojtsy</b> <<a href="mailto:gabor@hojtsy.hu">gabor@hojtsy.hu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>There is a small change in Drupal for 5.0.0, which enables you to provide<br>translations for the installer. By providing a ja.po, it.po, de.po, hu.po<br>etc for the default install profile (and copy the file into the default
<br>install profile folder), you can choose a foreign language in install<br>time. (An installer.pot file will be available).<br><br>Now if you have any foreign language PO files for the installer, it<br>assumes you are interested in the locale functionality and enables that
<br>module for you.<br><br>The question is how to process. The locale module should add some default<br>languages into the database to start with.<br><br>#1: Should the available installer .po files define what languages are
<br>added by default? Ie. if I have de.po, it.po and hu.po files in the<br>default profile folder, I would have German, Italian and Hungarian<br>languages setup automatically during install time?<br><br>Once the language is set up, we should automatically import translations
<br>for enabled modules.<br><br>#2: How and when should we import translations? We might get away with<br>enabling the locale module first strictly before any other module. Then if<br>any other module is later enabled (system.module
would be the second), we<br>would look for .po files in the "po" subfolder of that module (just like<br>these are placed in contrib modules) and import the .po files for enabled<br>languages, if available.<br><br>
#3: How should contrib modules handled? Should Drupal look for .po files<br>in the po subfolder and import into the already set up languages? What to<br>do with multimodule bundles, where you don't need to enable all modules
<br>(like links or ecommerce)? If you provide one .po file for the bundle,<br>then you have many stuff to import, without a clear reason... Should we<br>support payment-module.de.po type of filenames? Should we migrate to using
<br>these type of filenames only, so that simple de.po files will not work<br>for standalone modules?<br><br>#4: How should updates get covered? Should the module import the new<br>translations over the old ones? We have no information to clear
<br>translations from the database (no data to look for what translation<br>corresponds to what module, and many translations are used in multiple<br>modules). If we import new translations over the old ones, possible user
<br>customizations will get lost. If we only import new strings, updated<br>(fixed) translations will not get into the DB. Should we tell the user to<br>do database backups, and sidestepp this issue with overwriting all<br>
imported strings?<br><br>#5: There is an effort to support uninstallation. It is still a good<br>question, how would that fit with locales. See questions #4 above.<br><br>I would very much value your opinions. I intend to submit a patch for
<br>Drupal as soon as possible, so we can get automatic PO import in 5.0.0.<br>Unfortunately it is not possible to create a patch, if most of the above<br>questions are still open.<br><br>Gabor<br>_______________________________________________
<br>translations mailing list<br><a href="mailto:translations@drupal.org">translations@drupal.org</a><br><a href="http://lists.drupal.org/mailman/listinfo/translations">http://lists.drupal.org/mailman/listinfo/translations
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Alexandre Racine<br><a href="http://www.gardienvirtuel.com">www.gardienvirtuel.com</a> - Sécurité informatique<br><a href="http://www.salsamontreal.com">www.salsamontreal.com
</a> - La référence Salsa!