Could you please give translators a hint when string freeze will happen? As CCK for German is now 100% I'd like to keep it at 100% in the final version. So please give a hint of you change strings from now and give translators some time before final to update if there are changes from now.

Comments

yched’s picture

yched commented

Things like 'string freeze' are not as formalized in contrib as they are in core, where there are more people to test, report bugs early, fine-tune the UI, submit and review patches...
CCK being in RC stage doesn't mean we'll avoid string changes at any cost. Some just happened in the last few days/hours, others probably will later on. Simple question of manpower.

I propose that :
- we use this issue as a way for cck maintainers to notify translators of string changes
- we state that a final CCK-6.x-2.0 release has to wait at least 2 weeks after the last string change.

How does this sound ?
Damien, I know the french translation is also +-100%, what do you think ?

yched’s picture

yched commented

Starting now :-/
http://drupal.org/cvs?commit=125577 - change in a help text

karens’s picture

karens commented

http://drupal.org/node/273502 will involve a string change.

hass’s picture

hass commented

Thank you very much for the links and keep us posted if possible. 2 weeks after last string change and before final release sounds very good! It wouldn't take so much time, but we could write here when we are ready...

yched’s picture

yched commented

http://drupal.org/cvs?commit=125631 - string change in an error message.

hass’s picture

hass commented

Shouldn't we drop the single translation files in the translations folder yched copied over? They are completely outdated and only contains a few old strings not changed. All maintainers from these files need to spend their time first and also split the files per submodule and so on... i think we shouldn't deliver this outdated files to users. If a maintainer like to update he/she could also take the files from D5 or D6 1.x dev and start over...

yched’s picture

yched commented

http://drupal.org/cvs?commit=125700 - new strings.

hass : agreed. Can you take care of that ?

yched’s picture

yched commented

http://drupal.org/cvs?commit=125809 - new string
http://drupal.org/cvs?commit=125822 - string changes

hass’s picture

hass commented

In all other strings you have changed the first word after the %name: to lowercase, but not here http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/cck/modules...

yched’s picture

yched commented

@hass : that string has been unified in the most recent patch as well.

yched’s picture

yched commented

http://drupal.org/cvs?commit=125960 - string change

yched’s picture

yched commented

http://drupal.org/cvs?commit=127369 - string change / new string

yched’s picture

yched commented

http://drupal.org/cvs?commit=127472 - string change (to a string already present in core)

hass’s picture

hass commented

Destination-agnostic display.
Could we also rewrite this sentence, please? I'm not sure of all CCK users are professors or higher experienced - I don't know... I have never ever heard the word "agnostic" nor the translation of this in my whole live. No idea what this is or could be. I need to find my lost Oxford dictionary... maybe I will have some luck with it or maybe I'm only to stupid to find a translation. Nevertheless sounds not very common.

yched’s picture

yched commented

@hass : this text is currently not visible at all - I wouldn't bother with this right now.
In fact, I should probably remove the t() around those.

dopry’s picture

dopry commented

http://drupal.org/node/286637 - string change.

yched’s picture

yched commented

http://drupal.org/cvs?commit=129651 - string change

karens’s picture

karens commented

http://drupal.org/node/273502 has a string change.

yched’s picture

yched commented

http://drupal.org/cvs?commit=132272 - strings removed :-) (see #14 and #15 above)

yched’s picture

yched commented

http://drupal.org/cvs?commit=132637 - new strings

yched’s picture

yched commented

Side note : I plan to release an RC5 as soon as #285138: CCK 6.x Cannot Be Set Up in Install Profiles gets in.

hass’s picture

hass commented

Updated translations. I really hope this is the last RC... :-(

yched’s picture

yched commented

@hass : so do I - we push RCs along as we fix important bugs and get tired of saying 'this bug was fixed wafter the last RC, please use -dev release'. This *should* be the last one...

hass’s picture

hass commented

OT: I only said this as I'm not using Alpha, Beta or RC in production and I really hope CCK will go out of the door very soon. I thought and was told "it is ready" in march... Are we really all waiting for views to be final!? :-(

aren cambre’s picture

aren cambre commented

subscribe. This issue seems to give guidance on when CCK will be released.

yched’s picture

yched commented

http://drupal.org/cvs?commit=134614 - new string

yched’s picture

yched commented

Forgot to notify :
http://drupal.org/cvs?commit=135643 - new strings.

yched’s picture

yched commented

We are now quite close to a final release - matter of days. There are still a few fixes needed, but AFAICT none that imply a string change.

Translators are welcome to put the final touch on the translations (we only have french and german for now, I don't think we'll wait on others to complete)

Side note : currently french and german translations are scattered across multiple files - content.xx.po, includes.xx.po, general.xx.po, modules/yy/translations/yy.xx.po...
None of my business, but I guess it would be best for end users to group them into one single file, right ?

hass’s picture

hass commented

It is the intention to have one file per submodule. This allows Drupal to automatically import the translated strings of active modules *only*. This is the main sense of this splitting and is the way how Gabor designed this import stuff.

THX for notification. I will update German asap to the latest level.

yched’s picture

yched commented

Right, I forgot about automatic translation import.
What about includes.xx.po, general.xx.po ? will they be automatically imported too ?

hass’s picture

hass commented

Yes, if content.module is activated.

karens’s picture

karens commented

I committed #196468: Facilitate importing content types and fields and just realized there's a new string in that patch.

hass’s picture

hass commented

KarenS: How far are we away from final 1.0? If there are only 1-5 string changes I would say we should wait before a release date. Than give us 48 hours for the final touches and then release. Is this ok?

karens’s picture

karens commented

I think we're mostly waiting for a decision about whether to include #234774: Use Webform's UI for field addition (which will have a number of string changes) or whether to release without that.

I'm not completely sure I understood your point above, are you saying you only need 48 hours, not 2 weeks, to finalize translations once we're ready to go?

hass’s picture

hass commented

Yes, I think so.

I said "give me 48 hours" only for the time lag between countries... I'd only like to prevent doing this final touches for a very few strings 5 times or more... It's mostly not a big job to translate 10-20 good English strings... but if you change 100 or so it would become a bigger job and we need more time than a few hours :-).

yched’s picture

yched commented

http://drupal.org/cvs?commit=137998 has a new string in content.install- hook_requirements(). I'd advise to wait a little before translating it : when Views RC2 comes out I'll update that string to refer to that specific release.

yched’s picture

yched commented

http://drupal.org/cvs?commit=138543 / http://drupal.org/cvs?commit=138543 : two new strings (appear in each field module)

yched’s picture

yched commented

http://drupal.org/cvs?commit=141444 - one new string.

hass’s picture

hass commented

When should I finalize for release?

karens’s picture

karens commented

String changes at #312546: Internationalization code review, #299706: add rules integration, #234774: Use Webform's UI for field addition, and one small change in http://drupal.org/cvs?commit=141677 to add the name 'Standard' for a normal fieldgroup.

I am pushing to see if I can get #119102: Combo field - group different fields into one ready before release, it would be a whole new module. It can go in initially without translation and add translation later since it's new.

I'm going to commit one more RC first because there are lots of changes in the CHANGELOG since the last RC and I want to have a chance to flush out any remaining problems, but after that I'd like to move as quickly as possible toward an official release.

hass’s picture

hass commented

I will take a look how many strings are inside 119102... maybe it's not so much work.

karens’s picture

karens commented

I had to make some string changes, sorry. The update process needed some fixes so I changed some of the strings in content.install to make it more clear and added some new messages in content.admin.inc to warn users about inactive fields in their nodes.

Also a small string change in number.module where I changed a warning that silently fixed wrong input to an error that forces the user to fix it. The text is the same as before except I removed the second sentence that says the value is being changed.

hass’s picture

hass commented

Could someone explain me the sentence "fields that move in unison", please? I have troubles to understand and translate this and have only a dark idea... May it mean that the collection can me moved as "union"? Maybe i find out when testing the module... but maybe not.

smk-ka’s picture

smk-ka commented

I'm a bit late, but... while working on another patch I've realized that CCK field validation error messages differ somewhat from those in core. Example:
Core:
!name cannot be longer than %max characters but is currently %length characters long.
CCK text.module:
%name: illegal value.

Notable differences:
- Emphasis: core doesn't emphasize the field name, only certain (failed or otherwise important) variable conditions.
- Sentences: core forms sentences and doesn't separate field names by a colon.

Which means that the message in text.module should be rewritten to something like:
@name contains an illegal value. (contrary to core, I think we still need to escape the field names).

Now, before driving somebody crazy, I'd like to politely ask about your opinion to edit CCK's error messages to follow those in core, or whether the current behavior is intentional.

yched’s picture

yched commented

Hm. Not untrue :-)
But unless people do think this is critical, I'd rather not embark in a general overhaul of CCK messages this late.
For next release ?

yched’s picture

yched commented

http://drupal.org/cvs?commit=147950 - New strings :-(
This is not a new feature for the sake of a new feature...

hass’s picture

hass commented

I'm not sure how many error messages this are, but I'd like to please you all - now after months of recurring changes to stop changing strings finally. I'd like to be ready :-). Next release sounds ok. I thought we'd like to release in end of September and now we are in end of October and I see no light... The latest German help text update need to be committed and there are also two new help files missing I need to translate within the next days. Last ~4-5 days I fixed around 150 broken strings + added the advanced help in German with all images in German and I know string translation was at 100% complete two months ago... :-( - so *PLEASE* keep it stable now and do not change anything anymore.

I'm also away for a short break next Friday to Monday (if you plan a release and/or do changing strings again).

yched’s picture

yched commented
Status: Active » Fixed

OK, now that we've released, let's call this fixed !

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.