Greg Knaddison just asked about this in IRC, and given D6's focus as "the i18n release," it's worth bringing this up, I think... Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal. a) Shall we go ahead and implement this policy again this release? b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1? -Angie
Angela Byron wrote:
Greg Knaddison just asked about this in IRC, and given D6's focus as "the i18n release," it's worth bringing this up, I think...
Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal.
a) Shall we go ahead and implement this policy again this release? b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1?
I'd prefer RC1 to picking a beta when we don't know how many betas there will be.
Umm, I think it would be kind of unfair to sorts to include some translations in core, but not others. Unless there are lots.... On Jul 2, 2007, at 5:32 PM, Angela Byron wrote:
Greg Knaddison just asked about this in IRC, and given D6's focus as "the i18n release," it's worth bringing this up, I think...
Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal.
a) Shall we go ahead and implement this policy again this release? b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1?
-Angie
On Monday 02 July 2007 18:11:13 dmitri wrote:
Umm, I think it would be kind of unfair to sorts to include some translations in core, but not others. Unless there are lots....
I don't know, is that lots?: http://drupal.org/project/Translations -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 14; Cramer, 12; Travis, 10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005) Linux User: http://www.xubuntu.org/ Drupal Fanatic: http://drupal.org/
I mean ones that would be included in core I doubt there are very many that are fully core-ready -d On Jul 2, 2007, at 6:36 PM, Jason Flatt wrote:
On Monday 02 July 2007 18:11:13 dmitri wrote:
Umm, I think it would be kind of unfair to sorts to include some translations in core, but not others. Unless there are lots....
I don't know, is that lots?: http://drupal.org/project/Translations
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 14; Cramer, 12; Travis, 10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005) Linux User: http://www.xubuntu.org/ Drupal Fanatic: http://drupal.org/
Hi,
Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal.
I'm all for a string freeze like the last time. Keeping the string freeze date in mind helped us get a lot of UI text fixes in which improved overall usability.
b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1?
I am a translator as well (German translation) and I think it was enough time to complete at least the most important parts of it. I'd like to propose something else, though: While translating, I get to read all the help text included in Drupal, and I noticed that most of those help texts are not very well written and even include factual errors (e.g. removed features, no mention of newly added features etc.). I'd like to cast a kind of "user interface text team" that especially takes care of such issues. We could for example set up a site with Drupal 6, enable locale module and use it to modify the english strings (english -> english "translation"). After we've fixed those strings, we can create patches against HEAD. Not sure if that's a good/practiable solution. Any suggestions? Konstantin Käfer – http://kkaefer.com/
Konstantin Käfer wrote:
<snip>
I'd like to propose something else, though: While translating, I get to read all the help text included in Drupal, and I noticed that most of those help texts are not very well written and even include factual errors (e.g. removed features, no mention of newly added features etc.). I'd like to cast a kind of "user interface text team" that especially takes care of such issues. We could for example set up a site with Drupal 6, enable locale module and use it to modify the english strings (english -> english "translation"). After we've fixed those strings, we can create patches against HEAD. Not sure if that's a good/practiable solution. Any suggestions?
Konstantin Käfer – http://kkaefer.com/
I have also experienced inconsistencies and difficult to understand texts during translation. However an English - English translation with Drupal as translation environment would not work for me. A Drupal 6 install for testing and my usual PHP development tools will do. But apart from the tools, I like to join forces to improve the usability of Drupal texts. Sutha
Angela Byron wrote:
Greg Knaddison just asked about this in IRC, and given D6's focus as "the i18n release," it's worth bringing this up, I think...
Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal.
a) Shall we go ahead and implement this policy again this release?
I'll like to continue the 'at RC1' string freeze policy with D6. With the D5 release is was enough time to complete the Dutch translation. We had a fully translated D4.7 to work from so we 'only' had to translate the changes. Sutha
Angela Byron wrote:
Greg Knaddison just asked about this in IRC, and given D6's focus as "the i18n release," it's worth bringing this up, I think...
Last release, we had a "string freeze" once we hit RC1. This meant that any clarifications/clean-ups/etc. to any user-facing text (help messages, form labels, etc.) were 'frozen' and couldn't be altered after RC1 was released, in order to give translators ample time to translate Drupal.
a) Shall we go ahead and implement this policy again this release?
I think it would be great.
b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1?
Unfortunately most Drupal core translations are not 100% complete, and even when they technically look like being complete, the quality leaves more to be desired. If you would find a low quality translation within the Drupal package, would you associate this low quality perception to the whole package? Do you have an idea on how the different languages can be quality-assured/controlled? Gabor
Op 3-jul-2007, om 13:55 heeft Gabor Hojtsy het volgende geschreven:
b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1? Unfortunately most Drupal core translations are not 100% complete, and even when they technically look like being complete, the quality leaves more to be desired. If you would find a low quality translation within the Drupal package, would you associate this low quality perception to the whole package? Do you have an idea on how the different languages can be quality-assured/controlled?
Gabor Well, wouldn't that be the same as reviewing a patch? I would step up to volunteer for having a full Dutch translation in core, and perhaps there are more people who would like to help.
Stefan
Stefan Nagtegaal wrote:
Op 3-jul-2007, om 13:55 heeft Gabor Hojtsy het volgende geschreven:
b) Is RC1 enough time? If we set it at beta-2 or something would that allow us to include a few translations in Drupal core itself by RC1? Unfortunately most Drupal core translations are not 100% complete, and even when they technically look like being complete, the quality leaves more to be desired. If you would find a low quality translation within the Drupal package, would you associate this low quality perception to the whole package? Do you have an idea on how the different languages can be quality-assured/controlled?
Gabor Well, wouldn't that be the same as reviewing a patch? I would step up to volunteer for having a full Dutch translation in core, and perhaps there are more people who would like to help.
Stefan
Stefan, you are very welcome to joint the team of Dutch translators ;) With the Dutch D5 core translation Hendrik did a fine job on quality control. This model worked quite well. One main translator (my selves) assisted by a few people for checking and testing. Hendrik did the final check and committed the files. Although we did not have a formal RTBC cycle it could have been one. Al that matters is the quality of the translators. It helps to have a word list for consistency, involvement of experienced translators and a forum to discuss translation issues. But combining different styles of individual translators, good consistent wording, etc. just requires a consistent approach and skill. Sutha
participants (8)
-
Angela Byron -
dmitri -
Earl Miles -
Erik Stielstra -
Gabor Hojtsy -
Jason Flatt -
Konstantin Käfer -
Stefan Nagtegaal