http://groups.drupal.org/i18n Working group to drive work on i18n in Drupal en http://groups.drupal.org/node/12598 <p>Hi - I just found this group - these seem to be the right people :)</p> <p>Firstly a quick announcement - Language Sections is now available for Drupal 6 - a solution for a few problems, maybe - <a href="http://drupal.org/project/language_sections" title="http://drupal.org/project/language_sections">http://drupal.org/project/language_sections</a></p> <p>I'm looking for input from people who use Drupal for a multi-language site. What are the issues, in your experience? A typical problem, maybe, is how to have a View which elegantly handles the user switching languages (you can clone the View to make one version per language, but surely that's inelegant to say the least?)</p> <p>One specific topic - I guess that <em>dual</em> language (local language + English) rather than <em>multi</em> language is a common requirement. True or false? I've started a poll here - <a href="http://groups.drupal.org/node/12596" title="http://groups.drupal.org/node/12596">http://groups.drupal.org/node/12596</a></p> <p>My aim is to deliver a module which will eventually handle all "shortcomings" - I'm talking about <em>content</em> translation issues, not the Drupal user/admin interface, which is already adequately handled. Right now I'm focused on Views and CCK, but maybe there are other common issues?</p> <p>The project is at: <a href="http://drupal.org/project/language_extras" title="http://drupal.org/project/language_extras">http://drupal.org/project/language_extras</a></p> <p>By all means reply here, but you have a specific <em>feature request</em>, please put that in the relevant section on the project page, thanks.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/12598#comments language languages translation content views cck Internationalization Fri, 20 Jun 2008 08:42:12 +0000 netgenius 12598 at http://groups.drupal.org http://groups.drupal.org/node/12596 <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/12596#comments languages Internationalization Fri, 20 Jun 2008 08:28:53 +0000 netgenius 12596 at http://groups.drupal.org http://groups.drupal.org/node/12592 <p>Hello,</p> <p>I'm building a multi-lingual site, where I would like different translation groups/roles to be able to work on their language (and only their language) to translate source content. In some cases translating in response to content being posted, and at other times originating the content.</p> <p>Of the current access control methods I've looked at, there are ways to control access based on Taxonomies, Node types, and individual nodes... I may be missing something, but is there a way to control access based on language aside from making people specify the language of the content through taxonomy?</p> <p>-KT</p> <div class="og_rss_groups"><a href="/translations">Translations</a></div> http://groups.drupal.org/node/12592#comments access control internationalization locale module Access Control Internationalization Translations Fri, 20 Jun 2008 06:10:54 +0000 Tshering@drupal.org 12592 at http://groups.drupal.org http://groups.drupal.org/node/12045 <p>Hi<br /> I am trying to use forum in a multi lingual site<br /> the problem is that i don't want the end user to select the language , i want it to be selected automatically by the "context" - i mean by the forum language</p> <p>i have set up 2 groups (one for each language)<br /> forum/1 - English<br /> forum/2 - Hebrew</p> <p>so when the user uses English site for example and enters forum/1 and presses on "add forum topic" , he needs to select the language, and i want this to be automated</p> <p>one way i can do this by is by hook_from_alter()<br /> is there another way ?<br /> am i the first who needs this ?</p> <p>Thanks , Avior</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/12045#comments forums i18n Internationalization Fri, 06 Jun 2008 07:43:31 +0000 avior@drupal.org 12045 at http://groups.drupal.org http://groups.drupal.org/node/11855 <p>The National Democratic Institute is looking for a creative and flexible programmer to <a href="http://www.iknowpolitics.org">build</a> <a href="http://mobileactive.org/texting-it-in">cool</a> <a href="http://www.aswat.com/">tools </a> that help our partners around the world create more transparent, accountable and democratic governance. The programmer will work with our ICT Team and our country teams to design and build software for governments, political parties, civic action groups and networks of political reformers. This is a great opportunity to be on the front lines of applying technology to politics in the developing world. NDI works in 65 countries and is a leader in using technology to strengthen democratic governance and increase political participation. On web projects we tend to be a drupal shop; previous work with drupal is highly desired.</p> <p>Job description here: <a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&amp;id=23&amp;jobid=176377&amp;company_id=15851">http://hostedjobs.openhire.com/epostings/jobs/company_id=15851</a></p> <p>More on NDI's ICT programs here: <a href="http://www.ndi.org/globalp/ict/ict.asp">http://www.ndi.org/globalp/ict/ict.asp</a></p> <div class="og_rss_groups"><a href="/washington-dc-drupalers">Washington, DC Drupalers</a></div> developer jobs nonprofit political washington dc Drupal for Activists and Campaigns Internationalization Washington, DC Drupalers Thu, 29 May 2008 20:33:36 +0000 jford 11855 at http://groups.drupal.org http://groups.drupal.org/node/11613 <p>Here's a blog post I wrote, highlighting 47 patches to Drupal 6 which enabled internationlization.</p> <p><a href="http://acquia.com/blog/kieran/ux-improvements-drupal-6-internationalization" title="http://acquia.com/blog/kieran/ux-improvements-drupal-6-internationalization">http://acquia.com/blog/kieran/ux-improvements-drupal-6-internationalizat...</a></p> <p>Cheers,<br /> Kieran</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/11613#comments Internationalization Tue, 20 May 2008 20:50:22 +0000 Amazon 11613 at http://groups.drupal.org http://groups.drupal.org/node/11590 <p>I need a sanity check. I have installed i8n and enabled it, and it is happy....but the functionality confuses me. The languages block is enabled and has English and Japanese. I have installed the Japanese .po file, and when one hits "Japanese" the Drupal system UI changes to Japanese but the node content does not. At the bottom of the page there is a "Japanese" button that changes to node content to the translated page. That does not change the menus. What I want is for the language block to change everything - the menus but more importantly, the content. Am I missing something or is it working like it's supposed to?</p> <p>Any thoughts are welcome! Thanks.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/11590#comments Internationalization Tue, 20 May 2008 07:04:06 +0000 ceege111 11590 at http://groups.drupal.org http://groups.drupal.org/node/11546 <p>I'm using Drupal 6 to create a translation site. The translations getting done on the site are of content, not the Drupal interface itself, but the issues I'm facing are probably the same as you would deal with when planning the I18n Server, which is why I'm asking about this here...</p> <p>I want to give each translator access only to his/her language(s) for translation. I can do this by creating perms for each language:</p> <div class="codeblock"><code>&nbsp; foreach (language_list() as $language){<br />&nbsp;&nbsp;&nbsp; $perms[] = &#039;translate &#039;.$language-&gt;name;<br />&nbsp; }</code></div> <p>and then creating user groups for each language. However, this seems instinctively like an inefficient method. Problem is, I can't think of a better solution.</p> <p>Have any of you dealt with this problem already? Do you have any better ideas for assigning translators to specific languages?</p> <p>Thanks in advance for your help!</p> <ul> <li>Lisha</li> </ul> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/11546#comments i18n l10n translation Internationalization Sun, 18 May 2008 10:49:18 +0000 lishevita 11546 at http://groups.drupal.org http://groups.drupal.org/node/10738 <p>Is there a way to automatically wrap all "translated" text with html tags? For example, the font for dz (Dzongkha/Tibetan) is really quite small compared to western fonts due to the possible height of characters in the language. It would be very useful to take any text and wrap it with tags so that I could then institute text formatting with a stylesheet, while not disturbing and western text that may be untranslated.</p> <div class="og_rss_groups"><a href="/translations">Translations</a></div> http://groups.drupal.org/node/10738#comments i18n usability Internationalization Translations Tue, 15 Apr 2008 19:51:35 +0000 Tshering@drupal.org 10738 at http://groups.drupal.org http://groups.drupal.org/node/10620 <p><a href="http://www.nooku.org/" title="http://www.nooku.org/">http://www.nooku.org/</a><br /> <img src="http://farm3.static.flickr.com/2042/2385504192_5d5279f788_b.jpg"></p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/10620#comments Internationalization Thu, 10 Apr 2008 18:20:05 +0000 Amazon 10620 at http://groups.drupal.org http://groups.drupal.org/node/10143 <p>First post here in this group, so a warm "Hi!" to everyone!</p> <p><strong>The background</strong><br /> I have been using the fantastic i18n module since a year back and recently installed i18n 5.x-2.2. I'm working on a multilingual intranet for my company. The interface language will always be set to the default language (English) by setting the Language Management setting to "Interface language is independent" while some node content (books) can be translated to other languages. Why, you might ask. In some countries documents regarding the benefits and obligations as an emplyee must be published in the native language.</p> <p><strong>The question/discussion</strong><br /> Anyway... I was not satisfied with the language switching block provided with i18n and have therefore disabled it. That leaves me with the option to show the available translations printed together with the $links at the bottom of the page (which it does by default). Is this the ideal solution for a language selection? No, because your visitors have to scroll down to the bottom of the page and choose their language (even if just once). Also, the languages are mixed up with some other options not related to translation; "Add child page" and "Printer-friendly version" in my case. The preferred way (as I see it) would be to place the language selection at the top right corner of the node content area. This is for two reasons. First, it will be placed in a position of the page where users easily can see it. Second, it clearly indicates that this language switch will not affect the whole page including the interface.</p> <p>So I added a custom function (the one below) in my template.php which shows available translations of the current node. I then call this function in my node-book.tpl.php file and place it at the top right corner of the node area at the same level as the $submitted variable is printed. "This content is also translated to Polish" would show on the English version of the node if both English and Polish translations would exist. This use of a function call inside a template file is not ideal - ideas for a better solution are welcome.</p> <p>For usability reasons I want to remove the languages from the $links variable and instead output the language selection in the way I have described above. I have located the translation_link() function that adds the languages to $links. How can I override that function without having to add my own intranet_link() function that overrides all hook_link() from other modules also?</p> <p>Alright, let's sum it it up.<br /> 1) $links should not be used to output available languages since it also shows options not related to translation.<br /> 2) Language selection, when not affecting the whole interface should be placed at the top of node area to make it easy to see for the user.</p> <p>It would be interesting to hear your opinion on this subject and my solution.</p> <div class="codeblock"><code>function intranet_i18n_translation_switch($node) {<br />&nbsp; // ET 080319<br />&nbsp; if (isset($node-&gt;translation) &amp;&amp; (count($node-&gt;translation) &gt;= 1)) {<br />&nbsp;&nbsp;&nbsp; foreach ($node-&gt;translation as $language =&gt; $translation) {<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $links[$translation-&gt;language.&#039;_translation&#039;] = array(<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#039;title&#039; =&gt; i18n_language_property($translation-&gt;language, &#039;name&#039;),<br /> &#039;href&#039; =&gt; i18n_default_language().&#039;/node/&#039;.$translation-&gt;nid<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; );<br />&nbsp;&nbsp;&nbsp; }<br />&nbsp;&nbsp;&nbsp; $output&nbsp; = &#039;&lt;div id=&quot;available-translations&quot;&gt;&lt;em&gt;&#039;.t(&#039;This content is also translated to &#039;).&#039;&lt;/em&gt;&#039;;<br />&nbsp;&nbsp;&nbsp; $output .= theme_links($links, array(&#039;class&#039; =&gt; &#039;translation-languages&#039;));<br />&nbsp;&nbsp;&nbsp; $output .= &#039;&lt;/div&gt;&#039;;</p> <p>&nbsp;&nbsp;&nbsp; return $output;<br />&nbsp; }<br />&nbsp; return false;<br />}</code></div> <div class="og_rss_groups"><a href="/usability">Usability</a></div> http://groups.drupal.org/node/10143#comments i18n switching language usability Internationalization Usability Wed, 26 Mar 2008 14:51:19 +0000 O_o@drupal.org 10143 at http://groups.drupal.org http://groups.drupal.org/node/9900 <p>I was under the impression that when selecting a language, from the language selection block (in drupal6), the content is also filtered to display only the nodes in the selected language</p> <p>This behaviour is also confirmed by this handbook page <a href="http://drupal.org/handbook/modules/translation" title="http://drupal.org/handbook/modules/translation">http://drupal.org/handbook/modules/translation</a></p> <div class="codeblock"><code>Use the language switcher block provided by locale module to allow users to select a language. If available, both the site interface and site content are presented in the language selected.</code></div> <p>(maybe this is not really for drupal 6.x as it states ??)</p> <p>I have also looked for any configuration setting that enables such a thing but found nothing ....</p> <p>I finally filled out a bug report <a href="http://drupal.org/node/233242" title="http://drupal.org/node/233242">http://drupal.org/node/233242</a> but did not get any response yet ...</p> <p>This is happening on a clean install so it could not be a bug originating from another module ...</p> <p>What is your experience, am I missing something obvious ??</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/9900#comments bug content translation locale locale module Internationalization Tue, 18 Mar 2008 19:25:37 +0000 GiorgosK 9900 at http://groups.drupal.org http://groups.drupal.org/node/9542 <p>I'll add multi language by use I18N for drupal6.1 plus GUI for add multilanguage<br /> and multiseletion use language in web.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/9542#comments SoC 2008 Internationalization Sat, 08 Mar 2008 15:00:31 +0000 oxygenerror 9542 at http://groups.drupal.org http://groups.drupal.org/node/9429 <p>The National Democratic Institute is looking for a creative and flexible programmer to <a href="http://www.iknowpolitcs.org">build</a> <a href="http://mobileactive.org/texting-it-in">cool</a> <a href="http://www.aswat.com">tools</a> that help our partners around the world create more transparent, accountable and democratic governance. The programmer will work with our ICT Team and our country teams to design and build software for governments, political parties, civic action groups and networks of political reformers. This is a great opportunity to be on the front lines of applying technology to politics in the developing world. NDI works in 65 countries and is a leader in using technology to strengthen democratic governance and increase political participation. On web projects we tend to be a drupal shop; previous work with drupal is highly desired.</p> <p>Job description here: <a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&amp;id=23&amp;jobid=176377&amp;company_id=15851" title="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&amp;id=23&amp;jobid=176377&amp;company_id=15851">http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspj...</a></p> <p>More on NDI's ICT programs here: <a href="http://www.ndi.org/globalp/ict/ict.asp" title="http://www.ndi.org/globalp/ict/ict.asp">http://www.ndi.org/globalp/ict/ict.asp</a></p> <div class="og_rss_groups"><a href="/washington-dc-drupalers">Washington, DC Drupalers</a></div> job developer DC Drupal for Activists and Campaigns Internationalization Washington, DC Drupalers Thu, 06 Mar 2008 00:00:09 +0000 ianschuler 9429 at http://groups.drupal.org http://groups.drupal.org/node/9420 <p>Hi!</p> <p>In D5, we introduced Autolocale module, enabling users to import translations after enabling module / during installation. However, this had few caveats, as timeouts on cheap shared hosts, etc.</p> <p>In D6, Autolocale is built-in core, using batch API and just works very well.</p> <p>What do you think next step should be? From my point of view:</p> <p>"Let Drupal automatically fetch translations from a server".</p> <p>Imagine an user, enabling a module. Drupal polls Drupal.org (or something else), downloads a translation, imports it. No need to download any package, packages for modules will be smaller.</p> <p>This could be done for installer and/or contribs.</p> <p>What do you think and how do you think we can do this?</p> <p>Just my $0.02:<br /> - Installer is a great place for this, contrib may not be (Translations are already packed with contribs)<br /> - Gabor mentioned (at DrupalCon in Boston) that it may be done using Localization client. Is it wise? Any other approaches?<br /> - I can imagine a very easy implementation using curl()/fopen()/xmlrpc() (having a failback) to query Drupal.org/... for a translation, download it, extract (how to do this without Archive/Tar.php?) and import.</p> <p>Please post your ideas so we can eventually get this to D7 :-)</p> <div class="og_rss_groups"><a href="/translations">Translations</a></div> http://groups.drupal.org/node/9420#comments internationalization locale translations Internationalization Translations Wed, 05 Mar 2008 22:09:57 +0000 meba@drupal.org 9420 at http://groups.drupal.org http://groups.drupal.org/node/9004 <p>I'm new to Drupal, I am about to create a multi-language site, I had to go with D5.7 since D6 is not yet compatible with many modules that I want to use.<br /> I've been researching drupal sites for a step-by-step guide , I found some information in drupal handbooks but I still have many questions:</p> <ul> <li> <p>the locale module allows to translate core drupal modules and strings, does the i18n module allow to translate any newly installed modules ? or is it just about translating content (nodes) ?</p> </li> <li> <p>I need to switch the direction of the theme depending on the selected language, what are the language variable available for me to check ? can I use this code in my theme files :</p> <p>switch ($user-&gt;language ) {<br /> case 'en':<br /> //load LTR stylesheets<br /> break;<br /> case 'ar':<br /> //load RTL stylesheets<br /> break;<br /> }</p> </li> </ul> <p>any help would be greatly appreciated :)</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/9004#comments arabic internationalization rtl Internationalization Tue, 19 Feb 2008 00:57:49 +0000 level09 9004 at http://groups.drupal.org http://groups.drupal.org/node/8768 <p>I was suggested to ask here why there are string not being translated of the page node? The string that are not being translated are page; title and body. Why is that and can I override it?</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/8768#comments Internationalization Sat, 09 Feb 2008 15:07:02 +0000 saul11 8768 at http://groups.drupal.org http://groups.drupal.org/node/8724 <p>Hello, we would like to release the Drupal press release in multiple languages to show case the internationalization capabilities of Drupal 6.</p> <p>The press release is available at <a href="http://drupal.org/press/drupal-6.0/en" title="http://drupal.org/press/drupal-6.0/en">http://drupal.org/press/drupal-6.0/en</a></p> <p><strong>Required/pending translations:</strong><br /> Hindi - <a href="http://drupal.org/press/drupal-6.0/hi" title="http://drupal.org/press/drupal-6.0/hi">http://drupal.org/press/drupal-6.0/hi</a><br /> Cantonese - <a href="http://drupal.org/press/drupal-6.0/yu" title="http://drupal.org/press/drupal-6.0/yu">http://drupal.org/press/drupal-6.0/yu</a><br /> Chinese (Mandarin) - <a href="http://drupal.org/press/drupal-6.0/zh" title="http://drupal.org/press/drupal-6.0/zh">http://drupal.org/press/drupal-6.0/zh</a><br /> Esperanto - <a href="http://drupal.org/press/drupal-6.0/eo" title="http://drupal.org/press/drupal-6.0/eo">http://drupal.org/press/drupal-6.0/eo</a><br /> Gujarati - <a href="http://drupal.org/press/drupal-6.0/gu" title="http://drupal.org/press/drupal-6.0/gu">http://drupal.org/press/drupal-6.0/gu</a><br /> Japanese - <a href="http://drupal.org/press/drupal-6.0/ja" title="http://drupal.org/press/drupal-6.0/ja">http://drupal.org/press/drupal-6.0/ja</a><br /> Norwegian - <a href="http://drupal.org/press/drupal-6.0/no" title="http://drupal.org/press/drupal-6.0/no">http://drupal.org/press/drupal-6.0/no</a><br /> Portuguese - <a href="http://drupal.org/press/drupal-6.0/pt" title="http://drupal.org/press/drupal-6.0/pt">http://drupal.org/press/drupal-6.0/pt</a><br /> Swedish - <a href="http://drupal.org/press/drupal-6.0/sv" title="http://drupal.org/press/drupal-6.0/sv">http://drupal.org/press/drupal-6.0/sv</a></p> <p><strong>Completed translations:</strong><br /> Arabic - <a href="http://drupal.org/press/drupal-6.0/ar" title="http://drupal.org/press/drupal-6.0/ar">http://drupal.org/press/drupal-6.0/ar</a><br /> Catalan - <a href="http://drupal.org/press/drupal-6.0/ca" title="http://drupal.org/press/drupal-6.0/ca">http://drupal.org/press/drupal-6.0/ca</a><br /> Dutch - <a href="http://drupal.org/press/drupal-6.0/nl" title="http://drupal.org/press/drupal-6.0/nl">http://drupal.org/press/drupal-6.0/nl</a><br /> French - <a href="http://drupal.org/press/drupal-6.0/fr" title="http://drupal.org/press/drupal-6.0/fr">http://drupal.org/press/drupal-6.0/fr</a><br /> German - <a href="http://drupal.org/press/drupal-6.0/de" title="http://drupal.org/press/drupal-6.0/de">http://drupal.org/press/drupal-6.0/de</a><br /> Hebrew - <a href="http://drupal.org/press/drupal-6.0/he" title="http://drupal.org/press/drupal-6.0/he">http://drupal.org/press/drupal-6.0/he</a><br /> Italian - <a href="http://drupal.org/press/drupal-6.0/it" title="http://drupal.org/press/drupal-6.0/it">http://drupal.org/press/drupal-6.0/it</a><br /> Spanish - <a href="http://drupal.org/press/drupal-6.0/es" title="http://drupal.org/press/drupal-6.0/es">http://drupal.org/press/drupal-6.0/es</a><br /> Romanian - <a href="http://drupal.org/press/drupal-6.0/ro" title="http://drupal.org/press/drupal-6.0/ro">http://drupal.org/press/drupal-6.0/ro</a> - Please alias to <a href="http://drupal.org/node/226145" title="http://drupal.org/node/226145">http://drupal.org/node/226145</a></p> <p>Please share with your reviewer and ensure it's done.</p> <h2>Language translations needed</h2> <p>Cantonese<br /> Gujarati</p> <h2>Where to put the translated press release</h2> <p>Please add the translation in a file to the issue <a href="http://drupal.org/node/221296" title="http://drupal.org/node/221296">http://drupal.org/node/221296</a><br /> Make sure a (node) title is contained within the document and all required html is added. Please test the file to smooth the publishing.</p> <p>The proposed structure for the press releases is as follows:<br /> <a href="http://drupal.org/press/drupal-6.0/%language-code%" title="http://drupal.org/press/drupal-6.0/%language-code%">http://drupal.org/press/drupal-6.0/%language-code%</a><br /> The links with language codes for the press release translations will be (an <a href="http://drupal.org/node/221296">issue has been created to get these pages created</a> with the correct url alias. Any translators who need access to these pages once they're created or have other questions related to posting translations should use that issue.):</p> <h2>Language translations which are being written and need review</h2> <p>German - Konstantin Käfer (kkaefer); Review: Peter Santo (linulo), Gerhard Killesreiter (killes)<br /> French - Louis Montagne - Af83 - review: millette, scor<br /> Spanish - Jose Reyero<br /> Portugese - José san Martin (Chuva Inc.)<br /> Arabic - Khalid Baheyeldin (kbahey)<br /> Chinese (Mandarin) - Jacob Redding recruiting<br /> Italian - Devis Lucato (translation completed) - review: Fabio Mucciante (TheCrow)<br /> Indian(Hindi) - Steve DrupalValueHosting<br /> Catalan - Robert Garrigos. Reviwers: Joan Martínez &amp; Clara Ripoll (done)<br /> Esperanto - Chuck Smith<br /> Swedish - Itangalo, zoo33, HansG, Fabian<br /> Norwegian - Sten Johnsen (stenjo) - review: Hilde Austlid (zirvap)<br /> Dutch - Erik Stielstra (Sutharsan) - review: kvantomme.<br /> Hebrew - Zohar Stolar (z.stolar). Review: Yuval Hager (yhager). Translation is done (still with placeholders).<br /> Japanese - Mori Sugimoto (Code Positive) - Review: Yoko Yamamoto (<a href="http://www.atta-project.net" title="http://www.atta-project.net">http://www.atta-project.net</a>)<br /> Romanian - Marcel Cozma (zet)</p> <div class="og_rss_groups"><a href="/romania">Romania</a></div> Internationalization Romania Thu, 07 Feb 2008 16:47:15 +0000 Amazon 8724 at http://groups.drupal.org http://groups.drupal.org/node/8560 <p>As D6 is getting really close and we all try to test "everyting" I stumbled into an "old friend". <a href="http://drupal.org/node/153950 ">This problem</a> started up like a bug/race between the globalredirect and the i18n module. In D6 that part of i18n is moved into the D6 core, so all you need to test/trigger it, is a D6 installation and the <a href="http://drupal.org/project/globalredirect">globalredirect module</a>. No I'm not so sure anymore, if it is a "D6 problem" and if it should be moved to D6 issues or if it still is a isolated globalredirect bug?</p> <p>I just want to be sure that the path-handling in D6 is as robust as possible. Is jose also the maintainer for the "core part" of i18n? "nicholasThompson" write that he is fully booked and don't have the time to look into the issue, and that's perfectly OK, but I want to get the i18n people's attention, and everyone else involved in making international sites, and maybe there is an other way to solve it.</p> <p>--<br /> Stein Magne<br /> <a href="http://smbjorklund.no" title="http://smbjorklund.no">http://smbjorklund.no</a></p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/8560#comments Internationalization Thu, 31 Jan 2008 00:08:20 +0000 steinmb 8560 at http://groups.drupal.org http://groups.drupal.org/node/7660 <p>Hello,</p> <p>My name is Andrew. I have been interested in internationalization since 2001 when I started handling the internationalization of IBM's software customer support website. At IBM I was in charge of both writing properly internationalized code in Java and Perl, as well as managing the localization project by interfacing with our translation team, so I've been exposed to the whole process from end to end. I'm especially interested in the CJKV locales, and of those my primary interest is Japanese. I'd like to help out the internationalization project if possible. In the past I've worked with the internationalization frameworks in Perl and Java, as well as IBM's ICU toolkit. I also wrote a message bundle format that used XML and XSLT. (Nice in theory, but not so nice in practice.) Please let me know if there is anything that needs to be looked at or worked on. I'm fairly new to Drupal, having just started working with it in August, but I'm a quick study.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/7660#comments Internationalization Thu, 13 Dec 2007 01:42:24 +0000 vaelen 7660 at http://groups.drupal.org http://groups.drupal.org/node/7372 <p>Hi !</p> <p>I've written a small module to mass-export nodes into XLIFF files because I needed a complete site-translation.</p> <p>It exports all nodes to "files/xliff_export" creating sub-folders for each node-language.<br /> Works with i18n and localizer nodes.<br /> It uses XLIFF Tools module.</p> <p>download here: <a href="http://ww1.peak.at/xliff_massexport.tar.gz" title="http://ww1.peak.at/xliff_massexport.tar.gz">http://ww1.peak.at/xliff_massexport.tar.gz</a></p> <p>Alexander.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/7372#comments xliff Internationalization Thu, 29 Nov 2007 19:01:06 +0000 elek@drupal.org 7372 at http://groups.drupal.org http://groups.drupal.org/node/7268 <p>Hi Gabor et. al,</p> <p>I'm starting to play with the D6 beta 3 and I'm loving it. Hopefully I'll be able to contribute something, even if only use cases and a some patch review.</p> <p>I am having trouble with a locale/internationalization issue. Is this a good place to post?</p> <p>Having installed D6 beta 3, I ...</p> <p>a) created a story node with some text in english,<br /> b) enabled the locale and translation modules<br /> c) enabled imported the D5 french localization of the site (which got the vast majority of interface strings),<br /> d) did my own special ;-) version of a french version of my story node<br /> e) went into my user 1 profile and switched my preferred language to French.</p> <p>The problem (interesting feature?) is that now when I view the site, it's mostly in English even though French is specified as my user's language. However, whenever i view an 'edit' tab for the story node, the -interface- (including navigation menu) is translated into French. That's cool, but then I go back to the 'view' tab and i get the English translation again.</p> <p>Have I done something wrong? Is this a caching issue?</p> <p>regards!</p> <p>p.s. the q=node summary page shows both versions of the story. i love the 'each translation as node' model along with the tnid column in the node table. i can see how this is going to work well with other modules.</p> <div class="og_rss_groups"><a href="/i18n">Internationalization</a></div> http://groups.drupal.org/node/7268#comments Internationalization Fri, 23 Nov 2007 05:13:19 +0000 nally 7268 at http://groups.drupal.org http://groups.drupal.org/node/7043 <p>Copied from <a href="http://factoryjoe.pbwiki.com/FeedbackForDrupal6" title="http://factoryjoe.pbwiki.com/FeedbackForDrupal6">http://factoryjoe.pbwiki.com/FeedbackForDrupal6</a> so people can comment and act on it.</p> <p>Please help <a href="http://drupal.org/node/195518#comment-640500">turn the @TODOs into into tickets and patches</a>!</p> <h2>Installation</h2> <ul> <li>It's awesome that Drupal defaults to install.php if you haven't previously setup the site. That's a much better experience than having to know that you have to hit install.php first. Then again, it also means that you could be intercepted; unlikely but still something to consider.</li> <li>The first step of installation is to pick a language. While this of course makes some sense, I think it'd be better to invite folks into the installation process -- "Click here to get started" as a big button... and then below it have a link to "Learn how to install Drupal in another language." While I don't want to come off English-centric, I think it's a fairly safe bet that you can use English as the primary language for an intro graphic/text and then offer other languages down below -- heck even in other languages! <ul> <li>Yes. If there is a language pack, we should offer the selection as a first step. If not, we should start with the database page and provide a link about non-English installs there. This is easy. [chx]</li> <li>chx, I don't think this is a good idea, as it would clutter up the interface and would go unnoticed on the DB page. Chris' ideas seem to be better. [goba]</li> <li>I personally am pretty anti- useless screens you have to click through unless there's a significant usability increase. I'm not sure that's the case here. [webchick]</li> <li>I agree with goba &amp; webchick. An alternative is to have the introductory title and/or copy on the language page (1st step). This would make the initial install page 'friendlier' (which I think is Chris's point) without compromising clicks pages or usability. B/ **<b>@DONE: there's already a node covering language selection <a href="http://drupal.org/node/194444">here</a>.</b> - marco.h/robotangel</li> </ul> </li> <li>Configure Site page seemed too tall. There's a lot of help text in there that, at this point, is probably a bit superfluous, especially for creating the admin user. Why is the site email address different than the admin email, for example? Seems like they should really be merged and turned into a "create the first user" step. <ul> <li>We already have a JS to help with email addresses. <a href="http://groups.drupal.org/user/6860 chx">http://groups.drupal.org/user/6860 chx</a> <ul> <li>chx, the JS doesn't work well. as soon as you click out of the field, it copies over, and then it doesn't ever copy again [dmitrig01]</li> <li>This is by design, I believe. Otherwise it would be difficult to set <em>different</em> email addresses for site and admin. B/</li> </ul> </li> </ul> </li> <li>Shouldn't I set the Site Slogan here? <ul> <li><em>But the page is too tall? Yet you want to put more stuff in it? Requires a lot of text to explain where the site slogan appears.</em> [catch]</li> <li>Nope. [chx]</li> <li>The patch for this should change exactly 7 lines. Too big for Drupal 6? If not I'll do it [dmitrig01]</li> <li>I think setting the site slogan makes sense here, but this is subjective. Meh. B/</li> </ul> </li> </ul> <h2>Post Installation</h2> <ul> <li><del>The first thing I saw after I installed was a red, glaring error notice telling me to check the status report. </del> <ul> <li><em><a href="http://drupal.org/node/191310">#191310: committed</a> [goba]</em></li> </ul> </li> <li><del>The second problem was the creation of cron scripts.</del> <ul> <li><em><a href="http://drupal.org/node/100909">#100909: committed</a> [catch]</em></li> </ul> </li> <li>This is an extremely boring account page. Shouldn't there be some more basic details (please use vcard attributes!) <ul> <li>This is hardly what Drupal core needs to do. [chx]</li> <li>agreed with chx [dmitrig01]</li> <li>agreed with chx too, no superfluous functionality in core, please! [Liam McDermott]</li> </ul> </li> <li>Why can I block my own account? <ul> <li>Good question, add <code>#access =&gt; $user-&gt;uid != $account-&gt;uid</code> here. [chx]</li> <li>and an <code>&amp;&amp; $user-&gt;uid &gt; 1</code> for kicks [dmitrig01]</li> <li>Old issue on this: <a href="http://drupal.org/node/75289" title="http://drupal.org/node/75289">http://drupal.org/node/75289</a> (related is deleting: <a href="http://drupal.org/node/119683" title="http://drupal.org/node/119683">http://drupal.org/node/119683</a>) [add1sun]</li> </ul> </li> <li><del>The timezone picker seems unnecessarily verbose and overwhelming. Must it be so busy?</del> <ul> <li><em><a href="http://drupal.org/node/197442">#197442</a> [marco.robotangel]</em></li> <li>There are lots of timezones on this earth [dmitrig01]</li> <li>Instead of the current hour-minutes-seconds list ("12:12:00 +02:00") there could be simple list with locale names like "Europe/Helsinki", "Asia/Tokyo" etc. The current numeric, offset-calculated time selection index is confusing since the actual timezone name is unknown. This makes it difficult to have local deployment instructions etc., since there is no way to refer to a constant selection. Ideally, there should be only one selection for "Server location" (geographic area), which would offer default values for timezone, date &amp; time formats and maybe UI and content languages. [htalvitie] </li> <li>I like the idea of selecting time zone instead of offset. But my server is located abour 5,000 miles away from me so not sure how that'd work [catch]</li> <li>Has an issue or patch been created for this? B/</li> <li>There have been issues created in every Drupal version since at least 4.7, but we don't have a good source of timezone names or functions to do anything with them until PHP 5.2, so this can't be done in core until Drupal 7. An interim solution is going into the 5.2 version of the Date API which will overload these forms to set timezone names. [KarenS]</li> </ul> </li> </ul> <h2>Create Content</h2> <ul> <li><del>The Create Content page hasn't changed much... I wonder if you couldn't use icons in there to indicate different content types? And aren't Stories just blog posts? Why not use the more common terminology?</del> <ul> <li><em><a href="http://drupal.org/node/197765">#197765</a> [marco.robotangel]</em></li> <li><em>because the "blog" content type is reserved by the blog module, which should only be used for multi-user blogs, not simple one-person blog sites. This is indeed confusing, probably solved by removing blog.module from core [catch]</em></li> <li>This is Drupal, not WP. People define their own content types. Often those people aren't designers, so icons don't work. [dmitrig01]</li> <li>Although there could be a sensible set of default icons, with the ability to upload more as the admin add their own content types (bit of a 'patches welcome request really :) ). Also a more destcriptive name for 'story' could be 'article'. [Liam McDermott]</li> <li>or 'news', as the 'story' contents are promoted to frontpage by default [elv]</li> <li>I agree 'story' is not as good as it could be. I think 'article' is the best suggestion so far. B/ **<del><b>@DONE: search/create patch/issue</b></del> <ul> <li><em><a href="http://drupal.org/node/197765">#197765</a> [marco.robotangel]</em></li> </ul> </li> <li>What about the ability to add an icon on the "add content" or "edit content type" page. Then the icon could be used through out the site and configurable? Default icons for core content types would go a long way for newbies and wouldn't really get in the way as long as we can turn them off or better yet replace them. [mhofmockel]</li> </ul> </li> </ul> <h2>Creating a story/page</h2> <ul> <li>Wow! The Parent Item listing is huge! Sup with that? I haven't created any content and I'm already lost! <ul> <li>This is like saying "There are a lot of menu items!" [dmitrig01]</li> <li>Yes but - some solutions would be to use Ajax to only show the top level at first and then second levels, etc. OR we could make including menus in that dropdown optional and default only primary links to show there. [greggles]</li> <li><a href="http://drupal.org/node/191360">Menu parent choosers</a> [chx]</li> <li>Do drupal developers &amp; admins still customize or add to the navigation menu? I haven't ever worked on a project where the navigation menu was madeavailable for non-admin users. What if only the primary, secondary and other custom menus are available in the node-edit &amp; node-add forms by default? Additionally menus could be enabled and disabled. (This could be per role and/or per node type.) I think there is a contrib module that does this. <strong>@TODO: Find the module and get this module/feature into d7 core?</strong> B/</li> </ul> </li> <li>I notice the auto-search users on the authoring input, but frankly, if I only have a few authors, I'd rather have a dropdown... would it be possible to do a mixed input where I could type and get autocompletion OR have a dropdown or people selector to pick an author from a list? Sometimes I don't know people's usernames off the top of my head! <ul> <li><em>there's been work elsewhere to make dropdowns/autocomplete dependent on cardinality, user.module maybe? If so should be used here as well for less than 10 users or something[catch]</em></li> <li><code>if (db_result(db_query_range(&#039;SELECT COUNT(uid) FROM {users}&#039;, 0, 11)) &gt; 10)</code> use an autocomplete otherwise use a select box [dmitrig01]</li> </ul> </li> <li>Authored On should be a calendar picker. <ul> <li>Contrib. [chx]</li> <li>Specifically, <a href="http://drupal.org/project/jstools">JS Calendar in the JS Tools package</a>. B/</li> <li>Better yet, the jQuery calendar picker -- now in the HEAD of Date API to become the 5.2 version of the Date API, and hopefully in core by D7. [KarenS]</li> </ul> </li> <li> <p><del>Under Publishing Options, Sticky at top of lists still sounds confusing. Maybe stays at top of content lists?</del></p> <ul> <li><em><a href="http://drupal.org/node/197460">#197460</a> [marco.robotangel]</em></li> <li>Good idea. [chx]</li> <li><em>hmm sticky is used in a lot of forum software, I think people know what it means, maybe just "sticky" though, cut the rest</em>[catch] <ul> <li>I disagree. Not everyone using drupal has used forums extensively enough to understand 'sticky'. The term took me several months of drupal development to understand. B/</li> </ul> </li> <li>A good compromise could be: 'Sticky (stays at top of content lists).'</li> <li><del><strong><b>@DONE: search/create issue/patch</strong></b> B/</del></li> </ul> </li> <li> <p>I really don't like where Revision Information is located... If you're going to offer that feature, might I suggest you follow <a href="http://www.flickr.com/photos/factoryjoe/1935709237/">Writeboard's</a> lead and move the Revision checkbox and note closer to the document (only show the note section if Revision is checked)?</p> <ul> <li>Again, this is Drupal, not basecamp. We are configurable. Writeboards are not [dmitrig01]</li> <li>the Logs field has always been space that hardly anyone uses, hiding it until revision is checked makes sense. Furthermore publishing options isn't the most coherent set, moving revisions out of it (without asking the user to do a form_alter or form theming) is a good idea i think [ben-agaric]</li> </ul> </li> <li><del>Still not crazy about Input Formats. Even if you allow lots of control, I really wish that Drupal just picked one and stuck with it. If someone wants to override it in the admin sections or in their personal settings, that's fine, but doing it on a per-item basis just seems overly complicated.</del> <ul> <li>This is Drupal, not WordPress. [chx]</li> <li><em>why not just "filtered html" configured by default then let the user configure others?</em>[catch]</li> <li>I think Filtered HTML and Full HTML are basic sensible core formats. I believe "Input Format" could be just "Format", "Text Format" or "Body Format". And most important, I think it should be moved before Body as you usually choose this before you write the body. And also minor: The descriptions maybe removed as links to help are enough. It's wasted space after the first time you read them. Ideally, I'd wish for them to be a show-on-hover help. But that maybe not for core. [alienbrain]</li> <li><em><a href="http://drupal.org/node/48576">Issue about terminology</a> [elv]</em> <ul> <li><b>Resolved</b> B/</li> </ul> </li> </ul> </li> <li>Menu Settings is just odd. Instead of Menu link title, why not link text? <ul> <li>There are many links on the site. [chx] <ul> <li>How is that an answer? [dmitrig01]</li> <li>I think chx means that 'link' is an ambiguous term in drupal. B/</li> </ul> </li> </ul> </li> <li>Instead of Parent Item why not Section or Category? <ul> <li><em> look at the taxonomy module comments for why not category, section would be very misleading here</em>[catch]</li> <li>Short answer; Because Drupal is not Joomla!! :) lol B/</li> <li>Real answer; Taxonomy (the discipline and the drupal module/feature) isn't only about sections and categories. However, I agree that for most vocabularies (flat/non-hierarchical) 'Parent item' doesn't make sense. <strong><b>@</b>: search/create issue/patch</strong> B/</li> </ul> </li> <li><del>There's no discernible differences between the Story/Page interface. What's the difference again</del> <ul> <li><em>I think we could lose 'page' in D7, they're only there as examples - this is better handled in docs</em>[catch]</li> <li>I think we could lose 'story' [dmitrig01]</li> <li>Having the distinct static page and dynamic story (article, with author information, published to front page, and comments enabled) types by default is a good thing. They're just not labelled very well in my opinion, see my comment above. [Liam McDermott] agreed should be kept [ben-agaric]</li> <li>I don't think anything should change except the text; 'story' -&gt; 'article', and node-type description is also quite long. Can we communicate the same meaning more effectively in less words? B/ **<del><b>@DONE: search/create issue/patch to communicate the same meaning more effectively in less words</b></del> <ul> <li><em><a href="http://drupal.org/node/197825">#197825</a> [marco.robotangel]</em></li> <li>I disagree. In my opinion the description isn't too long. It describes what the type is meant for and gives examples what to create with it. Isn't this userfriendly?</li> <li><em><a href="http://drupal.org/node/197775">#197775</a> - a small addition to the story/article issue. Should be clear what is meant alone by reading the title then. [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Under comment settings, the language is confusing. Instead of Disabled, how about Off? For Read only, how about Closed? And for Read/Write, how about Open? <ul> <li>I completely disagree with this suggestion. the suggested terminology doesnt describe the functionality at all and in some way is misleading [litwol]</li> <li>I agree with litwol [dmitrig01]</li> <li>I don't think 'off' is an improvement on 'disabled'. However 'Disabled' isn't very clear. I thought of 'No comments' but I don't think it's any better than 'disabled' or 'off'.</li> </ul> </li> </ul> <h2>Administer</h2> <ul> <li>Wow, that's a lot of options! Yikes! <ul> <li>This is Drupal, not WordPress. [chx]</li> </ul> </li> <li><del>Ah, phew! Great to see the "hide descriptions" link...! Maybe they should be hidden by default and then turned on per section instead of all or nothing?</del> <ul> <li>Definately not. How would newbies orientate themselves without that help text? B/</li> <li><em>would make the page shorter, not a bad idea</em> [catch]</li> <li>I think so too. I wonder where this stuff is set. [dmitrig01]<br /> <em><b><a href="http://drupal.org/node/191502">Issue and patch here</a></b></em> [catch]</li> <li>Administer page huge usability boost: <b><em><a href="http://drupal.org/node/191825">Issue: Direct links to pages that are tabs within the listed pages</a></em></b> _{[ben-<a href="http://Agaricdesign.com/">agaric</a>]} <ul> <li>+1 for links to tabs on /admin, either in addition to, or instead of description. B/</li> <li>+1 for admin link saswell - possible make it red to warn users that theyre admin, and can break stuff? Would it be better to make an admin users, then a regular users who can post content, or would this add over-complexity to things? Nickweb</li> </ul> </li> </ul> </li> </ul> <h2>Content Management</h2> <h3>Categories</h3> <p>// <a href="http://drupal.org/node/192242">Forms tidied up</a>, <a href="http://drupal.org/node/193333">drag and drop is in</a>, <a href="http://drupal.org/node/192209">renamed back to taxonomy to avoid "Categories" confusion"</a>, <a href="http://drupal.org/node/190497">help text rewritten</a> - I've strikethroughed stuff that's been dealt with more or less. [catch]</p> <ul> <li><del>in the first sentence you mention the taxonomy module. Replace "The taxonomy module allows you to classify content" with "Categories allow you to classify content".</del> <ul> <li>covered above B/</li> </ul> </li> <li>Ugh, I remember "vocabularies". It's so Semantic Web it hurts.</li> <li>Perhaps you can move the "more help..." link into the main paragraph: "Read more..."</li> <li>Add vocabulary is a really terrible name. Why isn't it just "Add Category"? <ul> <li>Maybe because vocabularies are not categories. [chx]</li> <li>I think the terminology "vocabulary" is the confusing part. Categories are the new name for taxonomy, Term is fine, but the vocabulary part is the one that is confusing. Renaming that to "category item" or something else, may help, as long as it is not a "vocabulary". [kbahey]<br /> <del>* There's a consistency problem. The help text says "The taxonomy module allows you to classify content into categories and subcategories", but the only button is "Add vocabulary". [elv]</del></li> <li>Taxonomy &gt;&lt; Terms &gt;&lt; Vocabulary. Categories are merely a subset of 'Terms'. 'Categories' is a potential Vocabulary. The word 'Categories' has no place in the taxonomy module. In order to support drupal's killer feature (aka Taxonomy), drupal needs three different terms. The user needs to either know or learn a bit about taxonomy (the discipline) to understand this. <del><b><strong>@DONE: Can the help text be improved for d6?</strong></b></del> <em>See below</em>. Alternatively, offer some vocabularies by default to get started. Although thats what install profiles are for. <del><b><strong>@DONE: Create an issue on this for drupal 7</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203051">#203051</a> [marco.robotangel]</em><br /> <del> * The hint for "Vocabulary name" isn't very useful. Example: "Topic" doesn't really give me a hint as to what I should type... how about "Greg's Wedding" or "Technology" or "My Summer Vacation"?</li> </ul> </li> <li>I agree, but I think the example needs to include both a category/vocabulary name and a couple of terms that would be included. For example, "'Mammals' is a vocabulary whose terms could include 'dog', 'bear', 'mouse'. [Shai]</del> <ul> <li>Your example explains what a vocabulary is much more clearly than the current 'The name for this vocabulary. i.e. "Tags".' <del><b><strong>@DONE: search/create issue/patch for the above help text, and refine it.</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203029">#203029</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> </li> <li> <p>While I <em>kind of</em> understand why I should set Content Types here, I really don't. Why not just make them available to all Content Types?</p> <ul> <li>Because that would make the poor, poor node add screen even taller. Also because I might have vocabularies that are just not fit to certain content types. [chx]</li> <li>Does the node type selection need to be required? Isn't it possible to use the taxonomy module for more than categorizing nodes? [dwees]</li> <li>Yes. Taxonomy.module can be used to categorize entities other than nodes. <em> and it's not required here</em><br /> <del>* Hierarchy: This is where it gets screwy. I believe we talked about this before too. Why not make all Vocabularies multiple and just leave it at that?</del></li> </ul> <p><del>* Related terms: Why not just enable by default? The Help Text here is also not helpful: "Allows related terms in this vocabulary." Uh, duh?</del><br /> <del>* Free tagging... Ok, this seems like a good feature, but is confusing. It sounds to me like this is an interface feature. Why not remove the hierarchy option and ask: "Hierarchical Terms or Tags"?</del><br /> <del> * I think one could start with a hierarchy of terms, then turn freetagging on, so both would be used? [elv]</del></p> </li> <li>Multiple select is the provence of tags, so if you've got tags, you've got multiple select (forcing one tag isn't really folksonomic, now is it?). If you want multi-select in your hierarchy, ask in the hierarchy section.<br /> <del>* <em>Reckon a lot of this could be made simpler with just an 'advanced options' fieldset</em> [catch]</del><br /> <del> * I Agree. <strong>@TODO: search/create issue/patch</strong> B/</del><br /> <del>* Required. Ok this is fine. But you used the word node.</del><br /> <del>* Reference to node removed, see <a href="http://drupal.org/node/191104" title="http://drupal.org/node/191104">http://drupal.org/node/191104</a>. [keith.smith]</del><br /> <del> * For weighting, I wonder if you couldn't simply move this aspect out to the main Categories page -- sorting visually, rather than by number, as in Mephisto.</del><br /> <del>* Quicksketch is working on table row dragging. [chx]</del></li> </ul> <h3>Adding terms</h3> <ul> <li>Okay, a term is clearly a category... but this is not clear from the labeling.</li> <li>Why do I need a description for a term? AND for a vocabulary? <ul> <li>If Drupal core does not display this anywhere (does it?) then why it holds it? If a contrib module wants to do something with maybe it can provide the table, too? [chx]</li> <li><em>Always used to in rss feeds, now it does it at the top of taxonomy/term pages - patch went in this week [catch]</em></li> </ul> </li> <li>What are Synonyms used for? <ul> <li>See above. Yes, a full blown taxonomy needs these, but a full blown taxonomy does not get you laid or something so we might not want to keep it. [chx]</li> <li><em>There's a nice issue against D7 for using synonyms to catch free tagging bloopers, would save me several hours per year cleaning out mis-spellings etc., if that can be done simply in contrib then yeah, lose it from core</em> [catch]<br /> <del>* Again, visual weighting seems preferable here.</del><br /> <del>* It would be neat to organize the taxonomy term weights much how the drag and drop blocks and menu system are done. [Rob Loach]</del><br /> </del>* Visual weighting would also remove the need for the awkward Parents combo box.</del></li> </ul> </li> <li>Related terms is useless until you've added more than one term. And, shouldn't Drupal calculate related terms? It seems odd to do this manually. <ul> <li>It depends how you use related terms... Setting it manually makes sense. [elv]</li> </ul> </li> <li>The actions on this page should be "Save term and add more..." and "Save term". Going back to the containing vocabulary is not possible without going to Categories and THEN to the vocabulary... <em>too many clicks!</em> <ul> <li>There is a breadcrumb but still this is a valid idea. [chx]</li> <li>I agree - there should be an "add terms" fieldset in the list terms section, with an autocomplete textarea for this and ahah submit so you can immediately drag and drop after adding. [catch]</li> <li>Isn't the breadcrumb enough? There's also the navigation block. Two buttons will generate more mistakes ("ah damn I'm back to the vocabulary") than it will save clicks IMO. [elv]</li> <li>I Agree. This improves navigate-ability. <strong>@TODO: search/create issue/patch</strong> B/</li> </ul> </li> <li>The Delete button for a term should be a text link. <ul> <li>Why? [chx]</li> <li>Probably because you're less likely to click it by mistake if it doesn't look like the Submit button. Especially as the buttons are next to each other. It has also been discussed a bit for node edition pages, in the usability group. [elv]</li> <li>There are arguments both ways here. Links next to buttons look funny and inconsistent. But having a button to submit-and-delete a form of data is contradictory. I think 'delete' shouldn't occur in forms. It should be a local task (<a href="http://groups.drupal.org/node/6923#comment-21498">but not a tab</a>), and a table-action on admin/content/node. B/</li> </ul> </li> </ul> <h3>Comments</h3> <ul> <li><del>Shouldn't Approval Queue be Moderation Queue?</del> <ul> <li>I agree. B/ <del><b><strong>@DONE: search/create issue/patch</strong></b></del></li> <li><em><a href="http://drupal.org/node/201490">#201490</a> [marco.robotangel]</em></li> </ul> </li> <li>It would be nice if, like WordPress, Drupal started off with a default page and a default comment, to show what content in the system looks like. <ul> <li><a href="http://drupal.org/node/79582" title="http://drupal.org/node/79582">http://drupal.org/node/79582</a> is one issue but I would swear that there was another issue about moving the message into a node. [chx]</li> </ul> </li> </ul> <h3>Content</h3> <ul> <li><del>Seems like a regular search box would be useful here in addition to the Filter box.</del> <ul> <li><em>yes it would, there's an issue somewhere. back here later with it hopefully</em> [catch] <ul> <li><del><b><strong>@DONE: search/create issue/patch</strong></b></del></li> <li><em><a href="http://drupal.org/node/201493">#201493</a> [marco.robotangel]</em></li> </ul> </li> <li>I think the filters could be vastly improved for usability. This is a good use-case for where design patterns would work and be useful; <a href="http://groups.drupal.org/node/7294" title="http://groups.drupal.org/node/7294">http://groups.drupal.org/node/7294</a> B/</li> </ul> </li> <li>Again, not having any default content is kind of a bummer. <ul> <li><em>one node to hold the default message maybe, but deleting any more than that would be a 'bummer' as well</em>[catch]</li> </ul> </li> </ul> <h3>Content types</h3> <ul> <li>Maybe offer a link to show all Content of each Content Type -- i.e. a link to a prefiltered content search? <ul> <li>Sounds like a direct link to admin/content/node where "type is xxx". [elv]</li> </ul> </li> <li><del>I will say that this section is fairly simple and straightforward, though I'm not sure it's entirely clear what content types are!</del> <ul> <li><del><b><strong>@DONE: improve help text in d6. search/create issue/patch</strong></b></del> B/</li> <li><em><a href="http://drupal.org/node/201566">#201566</a> [marco.robotangel]</em></li> </ul> </li> </ul> <h3>Add content type</h3> <ul> <li>Some typos: Replace It is recommended that this name begins with a capital letter and consists only of letters, numbers, and spaces. This name must be unique to this content type. with It is recommended that this name begin with a capital letter and consist only of letters, numbers, and spaces. This name must be unique. <ul> <li>Typos addressed by <a href="http://drupal.org/node/191073" title="http://drupal.org/node/191073">http://drupal.org/node/191073</a>. [keith.smith]</li> </ul> </li> <li><del>The machine name should be auto-generated onblur().</del> <ul> <li>Could be a good idea, but removes a tiny bit of flexibility. [elv] <ul> <li>It would still be editable after onblur() B/</li> <li><em><a href="http://drupal.org/node/201565">#201565</a> [marco.robotangel]</em></li> </ul> </li> <li><del><b><strong>@DONE: search/create issue/patch</strong></b></del> B/</li> </ul> </li> <li>Hyphens <em>should</em> be allowed! <ul> <li>Wouldn't it conflict with phptemplate .tpl filenames? [elv]</li> <li>Hyphens have been restricted for very good technical reasons (urls, filenames, database...) B/</li> </ul> </li> <li>Under Submission form settings, the minimum number of words should be a text input, not a dropdown. Why would you rename the Title and Body fields? Seems like unnecessary customization. <ul> <li>You might want to create a custom content type and rename the fields to make it even MORE obvious for a novice user. For example renaming title to 'Your Name', etc...</li> <li>Renaming the fields is definitely a good thing. The dropdown is ia good hint of what are "a lot" and "a few" for newcomers. [elv]</li> <li>I Agree. B/</li> </ul> </li> <li>What's the difference between Description and Submission Guidelines? <ul> <li>It's explained on the content type creation page, under the fields! [elv]</li> <li>Obviously Chris had a problem understanding that text. <del><b><strong>@DONE: search/create issue/patch to improve the help text</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202533">#202533</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Why not rename Workflow Settings to Default Settings? <ul> <li>I don't think this is an improvement. 'Default Workflow Settings' might be. Meh. B/</li> </ul> </li> <li>Seems like Create new revision should be renamed to revision control. <ul> <li>No. The default behaviour is exactly that, a new revision <em>is created</em>, not just the revision control enabled. [elv]</li> </ul> </li> <li>Comment Settings... OMGWTFBBQ?! Again, why so much customization? This is overwhelming! On/Off/Open seems sensible, but all this threading stuff? Moving comment controls around? I dunno, I'll let this one go, but it just seems like too much stuff! <ul> <li>This is Drupal, not WordPress. [chx]</li> <li>Agreed with chx, particularly when you consider comments are also forum posts. [Liam McDermott]</li> <li><em>I'm going to open an issue to remove "most recent first" as an option in D6 - it was used on groups.drupal.org for a while until there was a petition to take it off in irc. Views 2 is likely to allow for stuff like this anyway.</em>[catch]</li> <li><del><b><strong>@DONE: search/create issue/patch to move some of the more complex comments settings into 'advanced settings' fieldset</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202199">#202199</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> <h3>Post Settings</h3> <ul> <li>Number of posts on main page: This is where help text would make more sense beneath the title, rather than beneath the input box. Perhaps this should be a text input, with a maximum specified? <ul> <li>Here again a text input is less friendly to newcomers. [elv]</li> </ul> </li> <li>Length of trimmed post... How about Length of post preview? And instead of characters, you should use word-count, since that's what you used in Content Types! Consistency! <ul> <li>Makes sense to me. Trimming is way to cut posts to approx the same <em>visual</em> length, so characters are appropriate. Minimum post length is more about content, so words are useful because there's a huge difference between the number of characters in an english and a german sentence. [elv]</li> <li>Looking into this I wonder why "Length of trimmed posts" is not just "Length of teasers", and "Unlimited" is not just "Disabled". [gaele]</li> <li>If we use "Length of teasers", then Unlimited could become "Full post" or "Full content". [elv]</li> <li>Also, the trimmed post is not the teaser. Teasers have other fields that don't get trimmed by node_teaser() (which is what this setting applies too).</li> </ul> </li> <li>Preview Post... This is where one-line options would really improve Drupal's interface. All you need is the line: "Must users preview posts before submitting? Yes No " <ul> <li>Yes/No settings would require us to read the help text to know which one we want to check. Right now we can just read the title of the fieldset and the checkboxes text. [elv]</li> <li>What he means is moving the description to the label. [gaele]</li> <li><del><b><strong>@DONE: search/create issue/patch to remove radios, add checkbox 'User must preview posts before submitting'</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202538">#202538</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Why is there a reset to defaults option here? There are only three options?! <ul> <li>Even if there were only one option: the reset is helpful in case you forgot what the default was. [gaele]</li> <li>Other settings pages don't have 'reset'. Reset is useful here because tweaking 'Length of Trimmed posts' is tedious work. B/</li> <li>I think Chris thought 'reset' was the old-school <code>type=&quot;reset&quot;</code> button. B/</li> </ul> </li> </ul> <h3>RSS Publishing</h3> <ul> <li><del>You should really offer Atom.</del> <ul> <li>It is RFC 4287 now, indeed. [chx]</li> <li><b><del><strong>@DONE: search/create issue/patch</strong></del></b> B/ <ul> <li><em><a href="http://drupal.org/node/202018">#202018</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li><del>This section should be renamed to <em>Feed Settings</em></del> <ul> <li>Perhaps 'RSS Feed settings'? <del><b><strong>@DONE: search/create issue/patch</strong></del></b> B/</li> <li><em><a href="http://drupal.org/node/202020">#202020</a> [marco.robotangel]</em></li> </ul> </li> <li>FeedBurner integration would be a nice plus, but that's a little proprietary. <ul> <li><a href="http://drupal.org/project/feedburner" title="http://drupal.org/project/feedburner">http://drupal.org/project/feedburner</a> [chx]</li> </ul> </li> <li>The wording here is a little awkward. Number of items per feed... how many feeds are there? Why not just Default feed items? <ul> <li><em> Default feed items suggests some stock content in rss feeds if no posts in them. How many feeds? No way to count this, I have '00000s on my site</em> [catch]</li> <li>I think it is not obvious from the help text that drupal sites typically have several rss feeds. <del><b><strong>@DONE: search/create issue/patch to change 'Number of items per feed' to 'Number of items in each feed' and 'The default number of items to include in a feed.' 'The default number of items to include in each feed.'</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202026">#202026</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Remove XML from Display of XML feed items; instead how about Feed content? Also remove XML from the help text. <ul> <li><del><b><strong>@DONE: search/create issue/patch to change 'Display of XML feed items' to 'Feed Content' and 'Global setting for the length of XML feed items that are output by default.' to 'Global setting for the default display of content items in each feed.'</strong></b></del> B/ <em> - See 202026 - [marco.robotangel]</em></li> </ul> </li> </ul> <h2>Site building.</h2> <ul> <li>Wow, spartan. <ul> <li>WTF? B/</li> </ul> </li> </ul> <h3>Blocks</h3> <ul> <li>A preview of the section of the theme... I like that. What use are these generous preview areas if I can't drag stuff into them? <ul> <li><a href="http://drupal.org/node/181066" title="http://drupal.org/node/181066">http://drupal.org/node/181066</a> by quicksketch [chx] <ul> <li>Quicksketch (and everyone else IMHO) is missing the point here; A table doesn't make sense for organising blocks. Organising blocks is essentially basic layout design. Users should be able to click and drag example blocks within drupal regions, and from one drupal region to another. <strong>@TODO: A table is the wrong design pattern on admin/build/blocks (wireframe!)</strong>. Drag and drop rows doesn't fix that. B/</li> </ul> </li> </ul> </li> <li><del>Ok, it is nice that when I change the dropdown menu, the item moves... but I really should just be able to drag and drop these content chunks up and down to different sections.</del> <a href="http://drupal.org/node/181066" title="http://drupal.org/node/181066">http://drupal.org/node/181066</a></li> <li>This needs some work: If you want certain blocks to disable themselves temporarily during high server loads, check the "Throttle" box. You can configure the auto-throttle on the throttle configuration page after having enabled the throttle module. How about You can auto-disable certain blocks during high server load to reduce stress by enabling the "throttle" option. Perhaps Throttle should be enabled by default? <ul> <li>IMO default disable is OK. [chx]</li> <li><em>definitely ok - be default would see content disappearing arbitrarily from people's sites at default traffic levels for throttle.module. Do we need block throttling when they're all cached - in D7 maybe take it out and just throttle modules??</em>[catch]</li> <li>The suggested new wording is an improvement, though. [gaele]</li> <li><del><b><strong>@DONE: search/create patch/issue to fix the wording</strong></b></del> B/</li> <li><em>patch <a href="http://drupal.org/node/199890" title="http://drupal.org/node/199890">http://drupal.org/node/199890</a> [gaele]</em></li> </ul> </li> <li>The introductory text is useful, but it strikes me that the interface for managing blocks is halfway down the page!! Not to mention that, but when I apply my changes, the success notification shows up below the text. Totally not standard. It should be above the text. <ul> <li>In general we might want to move menu_get_active_help to the bottom of the page. But then, pressing end won't land you on a submit button... [chx]</li> <li>How often do people read this text? It should be possible to hide this text, just like "hide descriptions". See this discussion: <a href="http://groups.drupal.org/node/6297" title="http://groups.drupal.org/node/6297">http://groups.drupal.org/node/6297</a> [gaele]</li> <li>@chx and @gaele. No and no. Quote Chris; 'The introductory text is useful'. The issue is that there is a lock of consistency in location / layout of the error and status messages. I believe this is a theme-layer issue <del><b><strong>@DONE: search/create issue/patch to fix this in core themes</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202821">#202821</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>The list of themes here is really confusing. I don't get it. This is <em>not</em> where I should be picking my theme. <ul> <li><em>This isn't wordpress</em> [catch] ;)</li> <li>Do we really need to show <em>disabled</em> themes here. [elv] <ul> <li>No, I don't think so. <a href="http://drupal.org/node/192779" title="http://drupal.org/node/192779">http://drupal.org/node/192779</a></li> </ul> </li> </ul> </li> <li>Why isn't the name of the block a link? That's what I should click to configure the block. <ul> <li><em>yeah nice idea if it doesn't affect drag and drop</em> [catch] <ul> <li>It doesn't affect the drag and drop. B/</li> </ul> </li> <li><del><b><strong>@DONE: search/create patch/issue to make the title link-able, remove 'configure' from the operations column.</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202548">#202548</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li><del>Weight seems silly on this section when you're moving blocks around with Javascript anyway. Why not do this visually, as I've suggested for other sections? Again, Mephisto gets this right.</del> <ul> <li><a href="http://drupal.org/node/181066">#181066 committed</a></li> </ul> </li> </ul> <h3>Block configuration</h3> <ul> <li>Ok, another unnecessarily super tall page. <ul> <li><del><b><strong>@DONE: search/create issue/patch to collapse 'role' and 'page specific visibility settings'</strong></b></del> B/</li> <li><em><a href="http://drupal.org/node/202183">#202183</a> [marco.robotangel]</em></li> </ul> </li> <li>Setting a block title is weird. What's this? Use to display no title, or leave blank to use the default block title. Why can't I just leave it blank for no title? Perhaps this input should be filled in with the default value and then I can delete it to set it to blank? <ul> <li><em>panels 2 has the default title greyed out, with a checkbox to override - would be nice to have here as well</em> [catch]</li> <li>Excellent idea. The current situation makes you wonder what the default title is. Using his suggestion we could leave out the description all together. [gaele]</li> <li>Great idea <del><b><strong>@DONE: search/create patch/issue to do as gaele said</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202837">#202837</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>The fieldset and fieldset captions are redundant in this section</li> <li>The labels for page-specific visibility might be: <em>Show on these pages</em>:, <em>Don't show on these pages</em>:, and <em>Advanced*</em>. <ul> <li>Beginning with "Show" or "Don't show" is a good idea. Something like "Show on only the listed pages." and "Don't show on the listed pages. Show on all other pages."? [elv]</li> <li>See his labeling suggestion under "Post settings". The block configuration page has room for improvement too ("Page specific visibility settings": ugly language!). How about: Show block on these pages: All, except the listed ones / Only the listed ones. And how about: Users can control the display of this block: No / Yes, shown by default / Yes, hidden by default. I guess my point is: options should be short, clear, easily distinguishable. [gaele]</li> <li>The 'page specific visibility settings' needs a makeover. Why can't you have show on pages foo/*, but hide on pages foo/bar, and only show if php code returns TRUE? I don't think there's any logical or technical reason, it's just a UI oversight. <strong>@TODO: make wireframe for the block configuration page, or at least the 'page specific visibility settings' fieldset</strong> B/</li> </ul> </li> <li>Notably when you collapse all fieldsets, no "default" options are available. This seems odd. <ul> <li>There are several places in drupal where this occurs. Usability Guidelines and Design Patterns could help here. B/</li> </ul> </li> </ul> <h2>Menus</h2> <ul> <li>It's odd that the word list(s) has an optional es when menus is listed immediately after. Either this text should reflect the number of items in the list, or all plurals should show the optional es.</li> <li>This should be removed from the description: <em>Select an operation from the list to manage each menu or menu item.</em> as no operations are visible. <ul> <li>This is leftover from the old menu page and <del><b><strong>@DONE: needs to be fixed in d6</strong>.</b></del> B/</li> <li><em>The issue for this is here: <a href="http://drupal.org/node/195083" title="http://drupal.org/node/195083">http://drupal.org/node/195083</a> [rowanw]</em></li> </ul> </li> </ul> <h3>Add menu</h3> <ul> <li>Why should I <em>Remember to enable the newly created block in the blocks administration page</em>? <ul> <li>It's not trivial -- there are theme, region and weight selections to be made. Of course, we could offer the region and weight setting here for the default theme. <ul> <li>region, yes, the others don't make sense here. <del><b><strong>@DONE: add select list to optionally add the new menu's block to a region in the default front-end theme with weight 0 (d7)</strong></b></del> B/</li> <li><em><a href="http://drupal.org/node/202854">#202854</a> [marco.robotangel]</em></li> </ul> </li> <li>In its current location the <em>Remember...</em> is easily overlooked. [gaele] <ul> <li><del><b><strong>@DONE: move the 'remember...' text into the form-submit result page. Remove the 'Enter the name text entirely'</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202858">#202858</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> </li> <li>The menu name and title fields are reversed when compared with Blocks and other item creation interfaces. <ul> <li><del><b><strong>@DONE: swap them.</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203001">#203001</a> [marco.robotangel]</em></li> </ul> </li> <li>Also: labels for human-readable and machine-readable names are not consistently used throughout Drupal. E.g. in in Add content type "Name" is the <em>human-readable</em> name. [gaele]</li> </ul> </li> <li>Typo in help text: This name may consist of only of lowercase letters, numbers, and hyphens, and must be unique. should be ''This name must consist of lowercase letters, numbers, and hyphens, and must be unique. <ul> <li><del><b><strong>@DONE: fix this and submit patch</strong></b></del> B/</li> </ul> </li> <li>After adding the menu, it's not obvious how to add something to the menu. Provide a link beneath the Menu Items table to "add menu item" <ul> <li><del><b><strong>@DONE: Add link to admin/build/menu-customize/menu-[NAME]/add on form-submit</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203004">#203004</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> <h3>Add menu item</h3> <ul> <li>Why is the menu path and title order reversed again? <ul> <li><del><b><strong>@DONE: swap these</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203007">#203007</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Parent Item shouldn't show on this page, as I was adding the Menu Item to a specific menu. <ul> <li>You still need a parent from that menu. [chx]</li> </ul> </li> <li>Weight shouldn't be on this page; instead visual ordering should happen on the menu's page. <ul> <li>I would much prefer having both. See <a href="http://drupal.org/node/181126" title="http://drupal.org/node/181126">http://drupal.org/node/181126</a> [chx] <ul> <li>I suspect you are probably part of a minority of drupal developers (most drupal users aren't drupal developers). If 'weight' is important, that feature could be moved into contrib. B/</li> </ul> </li> <li><a href="http://groups.drupal.org/node/6923#comment-20246">A real hierarchical menu admin interface</a> <del><b><strong>@DONE: get this in core for d7</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/203010">#203010</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>A popup to link to an existing page might be useful (i.e. "create a link to an existing page"). <ul> <li>Hmmmm. Not sure how this could work in the UI <strong>@TODO: wireframing needed</strong> B/</li> </ul> </li> <li>ugh...! Why aren't hyphens allowed? <ul> <li>Just tried and used a hyphen, it seems to works. [elv]</li> </ul> </li> <li>in testing, I could create menu items with paths like my-path, mypath or test. Why? <ul> <li>Interesting, <a href="http://drupal.org/node/190867" title="http://drupal.org/node/190867">http://drupal.org/node/190867</a> complains about the opposite. [chx]</li> </ul> </li> </ul> <h2>Modules</h2> <ul> <li>It seems like this page should emulate WordPress' plugins page for consistency between platforms; i.e. Change enabled from checkboxes to links -- it's easier to detect a problem with a single plugin than if you enable a whole bunch at once. <ul> <li><em>No way! image enabling cck/views/devel modules one by one! yikes! Or "this isn't wordpress".</em> [catch]</li> <li>Lol! Agree. Although asynchronous-enabling could work. B/</li> </ul> </li> <li><del>Cron should run automatically here; why doesn't it?</del> <ul> <li>Why...? [chx]</li> <li>@chx - I don't think it's clear that cron needs to run every hour and not just once [dmitrig01]</li> <li>@chx - Why? Because "Update Status" displays a message with something about cron (update must have cron run to display available updates) and people may think that it is related to module administration as a whole. [José San Martin]</li> <li><del><b><strong>@DONE: run cron once when install.php has done it's thing (by including an image with src="/cron.php" or similar method)</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202354">#202354</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Core - optional and Core - Required seems odd... why not hide the Required modules and simply list the modules configurable modules? <ul> <li>Eaton has raised this already in IRC, I agree. You can't do anything with the required modules, why not make them #value. [chx]</li> <li><em>yes, good plan</em> [catch]</li> <li>See <a href="http://drupal.org/node/195859" title="http://drupal.org/node/195859">http://drupal.org/node/195859</a></li> </ul> </li> <li>Updates should be announced inline (see WordPress 2.3) <ul> <li><a href="http://drupal.org/node/197486" title="http://drupal.org/node/197486">http://drupal.org/node/197486</a></li> <li><del><b><strong>@DONE: now that update status is in core it makes sense to merge modules and update status pages and data. search/create issue/patch for this</strong></b></del> B/</li> </ul> </li> <li>I shouldn't be told after enabling modules that no newer versions are available; whenever I visit this page, I should be shown what's updates are available with download or automatic update links. <ul> <li>Is there any reason not to run update status on disabled modules? <del><b><strong>@DONE: search/create issue/patch</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/162788">#162788</a> - this seems to be an issue for quite a long time now... [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Throttle seems problematic here -- not that it shouldn't be offered, but that it should be on by default. <ul> <li>See my comment on block throttle: I disagree. [chx]</li> <li><em> again, imagine the support requests if we did this, <em>shudders</em></em> [catch]</li> </ul> </li> <li>As part of the success messages, it would be nice if it listed things like "new permissions are available for Module X" rather than forcing me to click on the opaque permissions link. <ul> <li><del><strong>@TODO: get <a href="http://drupal.org/project/adminrole">adminrole.module</a> (or similar functionality) in core for drupal7</strong></del> B/</li> <li><strong>@TODO: create wireframes for including perms-setting in the module-enabling process (d7)</strong> B/</li> </ul> </li> <li>There should be an option to auto-enable required modules (i.e. Locale and Content translation modules) <ul> <li>Last I checked, the dependency checker worked. So, huh? [chx]</li> <li><em>I think he means javascript selection of dependencies or something, or auto-enable on submit with aptitude styles message to let you know</em> <ul> <li><del><b><strong>@DONE: This feature would eliminate any doubt the user might have about dependency-enforcement/management. Which currently is not clear, as Chris demonstrates</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202364">#202364</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> </li> <li>Module uninstallation seems janky. Why not just delete from the modules directory? I don't understand this; not to mention that no modules were available for uninstallation. What might be more useful is a reset module which would clear the DB of settings and related data. <ul> <li>Apache must not be able to write modules directory. Clearing the database is not trivial, if the module does not offer hook_uninstall, there is nothing Drupal can do. [chx]</li> <li>@chx - I think it's unclear that you need to disable to un-install, and disabling doesn't delete content or anything like that</li> <li>**@TODO: improve the help text on the uninstall page. Possibly also on the main module page, eg "If you disable a module, check whether it needs uninstalling". OR EVEN BETTER -- when you disable a module, get a message saying "This module made changes to the database. If you want to completely remove it, go to Uninstall". Some handbook material on installing/uninstalling modules would be good too. I've just had a quick glance at the main handbook page on drupal.org and couldn't immediately find anything.... -- joachim</li> </ul> </li> </ul> <h2>Themes</h2> <ul> <li>again, showing updates inline would be preferred.</li> <li><em>default</em> is a weird name for the option... I understand the option, but perhaps it should be <em>use this theme</em> and a checkbox option to allow people to override the default theme? <ul> <li>This page needs a makeover; The checkboxes to enable and radio buttons for default are too far apart. They should be in the left-most columns (like modules page) and closer together. But the thumbnail image sets the row-height. Maybe two pages are needed; one for list of themes, thumbnails and 'enable' (like modules page) and another for links to 'configure', and to set the 'default'. <strong>@TODO: create wireframes for themes page/s</strong> B/</li> </ul> </li> </ul> <h3>Global Settings</h3> <ul> <li>wow, that's a lot of text.</li> <li>why are these fieldsets not collapsible? <ul> <li><del><b><strong>@DONE: make shortcut icon and logo fieldsets collapsible and collapsed. They are not frequently adjusted.</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202333">#202333</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>Site slogan should be set during installation if it's offered here. <ul> <li>Or not. [chx]</li> <li>Too many options during install is a bad thing, in my opinion. [Liam McDermott]</li> </ul> </li> </ul> <h3>Theme Configuration</h3> <ul> <li>the lock color icons are misaligned in Safari</li> <li>why are these fieldsets not collapsible? <ul> <li><del><b><strong>@DONE: as above</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202336">#202336</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>There should be some suggestions for creating the logo -- especially size suggestions... i.e. the shortcut icon should be 16x16 pixels. <ul> <li><del><b><strong>@DONE: add help text about shortcut icon size, and transparency in logo image</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202343">#202343</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> </ul> <h2>Site Configuration</h2> <ul> <li>Why is the menu repeated in the content and in the sidebar? Seems unnecessarily duplicative. <ul> <li>Because the content can show descriptions and can show icons if so themed. [chx]</li> <li>A page that exists just to show icons? That doesn't convince me. The descriptions are helpful though. [gaele]</li> </ul> </li> <li>Administration Theme... yay! On by default plz can has? <ul> <li>On? There is no on setting here. [chx]</li> <li>In the usability group there was discussion about creating an admin theme in core for D7. This could be the default. [gaele]</li> <li>NO. The administrative theme can be an abrupt interruption in an otherwise seamless experience on a site. [sepeck] <ul> <li>So can long forms that are tedious to scroll, and cumbersome UIs that can't be enhanced because of the theme-limitations! :) B/</li> <li>To quote others - This is Drupal. Drupal is complex and has lots of options. Once configured most users will not see huge forms, merely what they have rights to see. Removing options under the 'it must be simple because people are too' mantra is silly. [sepeck]</li> </ul> </li> </ul> </li> <li>Kind of dumb that I have to manually enable Blog APIs after enabling the module...! <ul> <li>Only if you use a third party blogging software, otherwise it is useless. Off by default reduces later issues. [sepeck]</li> <li><del><b><strong>@DONE: enhance module descriptions and help text to clarify when blog.module and blog api modules are needed</strong></b></del> B/ <ul> <li><em><a href="http://drupal.org/node/202326">#202326</a> [marco.robotangel]</em></li> </ul> </li> </ul> </li> <li>A lot of good stuff is in here that I think should be bubbled up; I don't have time to get into these now... <ul> <li>That's a shame. :( You're feedback is <strong>very</strong> valuable! Thank you so much! B/</li> </ul> </li> </ul> <div class="og_rss_groups"><a href="/usability">Usability</a></div> Internationalization Usability Sun, 11 Nov 2007 07:14:49 +0000 chx 7043 at http://groups.drupal.org http://groups.drupal.org/node/6878 <p>Hello, we are trying to get Drupal case studies, from show case sites by Geography. North America, South America, Europe, Asia, Africa - If the sites have a cross geographic element or are internationalized then that would be even better. The goal is to show that Drupal is being effectively used around the world.</p> <p>Drupal sites by Geography - <a href="http://drupal.org/node/88417#comments">Internationalization use cases</a></p> <h3>Top African Sites:</h3> <ul> <li><a href="http://www.afgri.co.za/">http://www.afgri.co.za/</a></li> <li><a href="http://abahlali.org/">Abahlali baseMjondolos - South African advocacy group</a> </li> </ul> <h3>Africa</h3> <ul> <li><a href="http://liberdadi.com/">Liberdadi - The Voice of Cabo Verde's People</a></li> <li><a href="http://www.filmmaker.co.za/planet/">Filmmaker</a></li> <li><a href="http://birds.intanzania.com/">A Beautiful Local Bridwatcher's Blog (Tanzania)</a></li> <li><a href="http://www.suuch.com/">Suuch Solutions - Drupal Web Development (Ghana)</a></li> <li><a href="http://burtronix.co.za/"> Burtronix - Drupal Programming and Web Development (South Africa)</a></li> <li><a href="http://www.fhsst.org/">Free High School Science Texts (South Africa)</a></li> <li><a href="http://jogmymemory.co.za/">South African application</a></li> <li><a href="http://www.newsudanvision.com/">New Sudan Vision</a></li> <li><a href="http://www.sanabelnetwork.org/">The Microfinance Network of the Arab Countries (Egypt)</a></li> <li><a href="http://www.parksegypt.org/">The Egyptian Ministry of State For Environmental Affairs, Natural Parks portal</a></li> <li><a href="http://www.hc-si.com/marketbeat">HC Web Presence (Egypt)</a></li> <li><a href="http://www.pwcmecareers.com/">PWC Middle East careers website (Egypt)</a></li> <li><a href="http://heikal-foundation.org/">The Heikal Foundation for Arab Journalism (Egypt)</a></li> <li><a href="http://sandseasailors.com/">An Egyptian Rally Team (Egypt)</a></li> <li><a href="http://www.nahdetmast.org/">Nahdet El-Mahrousa: A famous Egyptian NGO</a></li> <li><a href="http://manalaa.net/">Manalaa.net: Two famous Egyptian activists blog, Drupal free hosting, news aggregator, and other stuff</a></li> <li><a href="http://www.ghanathink.org/">Ghanathink</a></li> <li><a href="http://fienipa.com/">Internet Services For Cosmopolitan Africans.</a></li> <li><a href="http://www.southafricanwine.org">South African Wine</a></li> <li><a href="http://www.aboshamani.net">In the spirit of the cheetah private wildlife ranch</a></li> </ul> <h3>Asia</h3> <ul> <li><a href="http://voiceofchinese.com/">Voice of Chinese</a> Chinese community.</li> <li><a href="http://www.handchange.com/">Chinese social networking site. share pictures, videos, etc.</a></li> <li><a href="http://www.yingyudaxue.com "> University of English </a> online English study site for Chinese speakers</li> <li><a href="http://www.sooclass.com "> Chinese course site</a> An share education trainning information site</li> <li><a href="http://www.biany.cn "> BianY Chinese Dictionary</a> An open and popular Chinese dictionary</li> <li><a href="http://evance.name/"> Evance Park</a> the personal blog of a drupal fans,including drupal theming/resource , web-front tech and some personal words</li> <li><a href="http://qqschool.net"> QQschool.net </a> online community site of TaiYuan University Of Science and Technology . (Chinese)</li> <li><a href="http://www.thinkerspace.com"> Thinkers | Thinking Club</a> An online community of extraordinary minds. (Chinese)</li> <li><a href="http://www.geekg.com"> geekg</a></li> <li><a href="http://bodyss.com/"> Everything is Possible</a></li> <li><a href="http://www.radio86.co.uk/"> Chinese Tourism in 5 languages</a></li> <li><a href="http://asia.playstation.com/eng_hk/index.php"> Asian playstation - e.g. Hong Kong</a></li> <li><a href="http://haeundae.manseh.com/"> Korean haeundae</a></li> <li>Indonesia is the 9th most popular visitor to Drupal.org. In October they consumed 4.5% of bandwidth to Drupal.org, more than any Asian country.<a href="http://www.bpn.go.id/">Badan Pertanahan Nasional</a></li> <li>BUILT in the PHILIPPINES:</li> <li><a href="http://www.luenthai.com"> Luenthai Corporate Website</a> -- a company providing end-to-end apparel services that support our customers' speed-to-market goals. The website is also available in Chinese language.</li> <li><a href="http://www.zooomr.com/photos/rubencanlas/3743258/" title="Photo Sharing"><img src="http://static.zooomr.com/images/3743258_8c9e0e35b0_t.jpg" width="100" height="93" alt="newsmekong" align="left" hspace="5" /></a><a href="http://newsmekong.org/"> News Mekong</a> is a collaborative website of Asian journalists, focusing on covering Mekong news and issues.</li> <li><a href="http://www.shenzhenparty.com/"> Shenzhen Party</a> the most popular entertainment and city guide for Shenzhen, China</li> <li><a href="http://www.zooomr.com/photos/rubencanlas/3743326/" title="Photo Sharing"><img src="http://static.zooomr.com/images/3743326_8f8985add4_t.jpg" width="100" height="77" alt="shenzhen_buzz" align="right" hspace="5" /></a>The freshly minted <a href="http://shenzhenbuzz.com/"> Shenzhen Buzz</a> is a hip lifestyle guide on Shenzhen and China.</li> <li><a href="http://haribon.org.ph/"> Haribon Foundation</a> -- an environmental NGO in the Philippines. One of the earliest adapters of Drupal.</li> <li><a href="http://www.doh.gov.ph/"> Department of Health</a> -- the first government agency to switch to Drupal. DOH aims to use its portal to promote knowledge sharing. With its powerful taxonomy module and online collaborative modules, Drupal was the best choice for them.</li> <li><a href="http://swapinitiative.org/"> Swap Arts Initiative</a> is an independent art gallery.</li> <li><a href="http://kapwakomahalko.org/"> Kapwa Ko Mahal Ko</a> is a non-profit charitable institution</li> <li><a href="http://couchkamotereviews.ph/drupal"> The Couch Kamote Reviews</a> - Ahem! Shameless plug.<br /> All of the above 8 sites were built by the <a href="http://digitalsolutions.ph/"> Dig It All Solutions</a> team, whose site is also built on Drupal (and currently being revamped).<br /> <a href="http://www.zooomr.com/photos/rubencanlas/sets/25038/"> View more screen shots.</a></li> <li><a href="http://www.beibei.biz/"> beibei.biz</a> is a coffee club. (Chinese)</li> <li><a href="http://www.500959.com/"> 500959.com</a>, Provide blog, photo albums, books to read, pictures and other services. (Chinese)</li> <li><a href="http://e-info.org.tw/"> Taiwan Environmental Information Center</a> (Chinese)</li> <li><a href="http://www.lib.wfc.edu.tw/"> WuFeng Institute of Technology Library</a> (Chinese)</li> <li><a href="http://www.eb.wfc.edu.tw/"> Dept. of E-Commerce, WuFeng Institute of Technology</a> (Chinese)</li> <li><a href="http://www.coolloud.org.tw/"> Coolloud</a> is a local news provider/aggregator about social movement. (Chinese)</li> <li><a href="http://www.ma19.net/"> Ma19.net</a> is a website of Ma Ying-Jeou, 2008 Taiwan presidential candidate. (Chinese)</li> <li><a href="/freelinking/www.ibobar.com">Social networking site?</a></li> </ul> <h3>Europe</h3> <ul> <li><a href="http://www.glamourparis.com/"> International Magazine - french</a></li> <li><a href="http://www.myvideoplanet.com/"> “ The first video travel guide based on video reviews from travelers !” - english</a></li> <li><a href="http://iknowpolitics.org/"> International Knowledge Network of Women in Politics - english/spanish/french</a></li> <li><a href="http://ndipartidos.org//"> Red de Partidos Politicos - spanish/english </a></li> <li><a href="http://tube.e-pcmag.gr/"> Greek PC Mag</a></li> <li><a href="http://www.cossiolegnami.it/"> Italian industry site</a>, <a href="http://www.mc-coperture.it/"> corporate site of building (dampproofing) </a></li> <li><a href="http://www.kurir-info.co.yu/"> Balkans, Yugoslavia</a></li> <li><a href="http://www.cialog.com/">German design firm</a>, <a href="http://www.heiner-koepcke.de/">Photography firm</a>, <a href="http://debatte.welt.de/">Community debate site for german newspaper "The World"</a>, <a href="/freelinking/%255B%255Bhttp%253A%252F%252Fdiscoveryclub.de%252F">Discovery club -germany</a></li> <li><a href="http://www.spmp.org.pl/">Polish corporate</a></li> <li><a href="http://www.openquest.pt/">information systems portugal</a>, <a href="http://www.jf-requeixo.pt/" title="http://www.jf-requeixo.pt/">http://www.jf-requeixo.pt/</a>, <a href="http://www.pjn.pt/" title="http://www.pjn.pt/">http://www.pjn.pt/</a></li> <li>Czech republic <a href="http://www.dzm.cz"> DZM fashion brand shops //Drupal used for presentation not for E-shop</a></li> <li><a href="http://www.lyxfallan.se">The Luxtrap - show is about families struggling with their economy</a> - Swedish TV show site</li> <li><a href="http://www.pavlotabakov.com">Unofficial site of ukrainian singer Pavel Tabakov </a> - Ukraine (russian, ukrainian, english)</li> </ul> <h3>North America</h3> <h3>Caribbean</h3> <ul> <li><a href="http://pnud.onu.org.do/">United Nations Development Program at the Dominican Republic</a></li> </ul> <h3>South America</h3> <ul> <li><a href="http://www.openware.biz">Openware</a> Openware´s site 100% Drupal - Sitio de Openware 100% Drupal (Argentina)</li> <li><a href="http://www.difundefirefox.com">Difunde Firefox</a> - Portal de difusión del navegador de Mozilla</li> <li><a href="http://www.flashparty.org.ar">The Flash Party</a> Expo-competencia de Arte Digital (Argentina)</li> <li><a href="http://www.nuestromar.org/" title="http://www.nuestromar.org/">http://www.nuestromar.org/</a> - Sitio de noticias y servicios de la Fundacion NUESTROMAR, finalista Arroba de Oro </li> <li><a href="http://www.democratas.org.br/" title="http://www.democratas.org.br/">http://www.democratas.org.br/</a> - Democratas is a political party in Brazil, See more in <a href="http://en.wikipedia.org/wiki/Democrats_%28Brazil%29" title="http://en.wikipedia.org/wiki/Democrats_%28Brazil%29">http://en.wikipedia.org/wiki/Democrats_%28Brazil%29</a></li> <li><a href="http://deputados.democratas.org.br/" title="http://deputados.democratas.org.br/">http://deputados.democratas.org.br/</a></li> <li><a href="http://senadores.democratas.org.br/" title="http