Closed (won't fix)
Project:
Internationalization
Version:
7.x-1.0
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2011 at 13:54 UTC
Updated:
5 Apr 2012 at 20:09 UTC
Jump to comment: Most recent file
Comments
Comment #1
jose reyero commentedIt means strings with other text formats won't be handled/translated so they will be removed from our list of strings to translate.
Comment #2
batigolixThis is a clearer message, but I hope I understood well what the option does:
"The translation system only translates the strings in the selected text formats. All other strings will be ignored and removed from the list of translatable strings."
Comment #3
jose reyero commentedOk. Thanks.
Comment #4
batigolixDid you already review the UI of the i18n module(s) or is it too early for that? I found a second help text that could use a rewrite:
"If a text group is no showing up here it means this feature is not implemented for it."
at admin/config/regional/translate/i18n_string
The page is ambiguous about what I'm actually doing there: the tab says "strings", the title says "translate interface" and the main button says "refresh string".
I suspect this functionality is about loading strings in the database for translation, e.g. for when I have enabled translation of certain taxonomy terms. Is that right?
Comment #5
jose reyero commentedThough these kind of suggestions are appreciated, we cannot really spend half an hour for every string there. So please post all the improvements at once, if in patch form better.
Also you can help improving these pages, http://drupal.org/node/133977
Thanks.
Comment #6
batigolixfind attached a patch for 2 text improvements for the i18n_strings sub module
please check whether the meaning is still correct.
Comment #7
batigolixIgnore patch above. the new attached patch contains all my ui text improvements for all i18n modules.
I reviewed all the strings in the code, without seeing them in their context within the i18n admin screens. I also skipped the help texts. So a more profound review of the UI may be needed
Comment #8
jose reyero commented> I reviewed all the strings in the code, without seeing them in their context within the i18n admin screens ?
Really?
Please note that changing strings is a major headache for translators so we just fix mistakes and make needed improvements but we don't improve strings for them to look nicer.
The time to review module strings and make them look nicer was before the first stable relese.
Comment #9
jose reyero commented