Do not extract schema descriptions

I recently discussed that with webchick. One idea could be to implement two modes: the "standard template" will not extract schema descriptions nor strings from test cases; a "developer template" will extract everything.

As long as we have t() in there, Drupal itself will complain about untranslated strings in your database, and people will blame potx for not extracting those. It would possibly be good to backport that patch to Drupal 6 and remove the t() from Drupal 6 core. Then only some contribs are left, which actually provide schema descriptions with t(). I bet that does not affect too modules :)

I bet that does not affect too *many* modules that is :)

Subscribe - I'm not yet sure if I like this idea very much... especially after I've translated many modules and core. By one side it would be great to have less strings that needs to be translated - otherwise not. All modules I've translated have schema translations and this are many... or at least felt - many completed translations - I would guess 500 schema strings or much more. But having less strings sounds also alluring.

Maybe it's a better idea if we could extract the schema strings into an extra schema.pot and then let translators decide whether they like to translate the schema for schema API or not. l10n_server should show us the filename or that this is a schema translation...

@Pasqualle: You should re-read what I've said. Gabor doesn't talk about moving schema strings in "schema.pot". 500 already translated strings was only guessing - it could be 1000 or more and German is not the only complete translations (NL and many others are complete, too). Aside 500 strings ARE VERY MANY strings and I'm worried that all this strings should now go to /dev/null. I'm not expect so much changes in this strings - so it's mostly a one time translation, but I do understand that other teams complain if they have 2500 new/changed strings in D6 core and this is really why the German translation also have taken a long time (8 months) to become complete - but only a very small part of them was missing schema strings as schema strings are typically easy to translate.

@hass: Drupal 7 does not do any t() or st() on schema strings, so as Pasqualle says in #8 your translations are going to /dev/null sooner or later anyway. The point of backporting the removal of t() is to not waste *more* translator time on these strings, now that we've wasted enough. I did translate most schema strings for Drupal 6 core to Hungarian, and I am fine with the backport. I understand the reasons behind it, and I think it is superior to whatever amount of work I put into those strings. They will go extinct with Drupal 7 anyway. Why not stop others from wasting their times until then?

I have no idea why this strings shouldn't be translated and D7 shouldn't drop them. Schema API make use of them.

@hass: maybe it would be good idea then to read the issue which was referenced two times already above: #332123: Remove t() from all schema descriptions

The only good reason I see is "we also don't translate code comments". But they all forget about the Schema module that can show the translated descriptions.

@hass: I am summarizing the details of that issue for you there. I think it would be better to not discuss an issue in another one, when you can equally question the original issue on the original issue itself. There the people who were pro or against the change could reply as well. Instead of your complaints tucked away in a contributed module's queue.

Maybe extract schema strings into schema.pot file especially for Schema module?
But opposite this functionality should be included in schema not POTX.
So this issue should go to schema queue

But only POTX generates POT files for us... but as said - less strings are also fine as it's less work.

Moving the scope now that schema descriptions are not translated anymore.

But #332123: Remove t() from all schema descriptions still not applyed for 6-dev brunch

He may talk about simpletest tests... but not sure why the topic was changed to test case strings.

@Damien Tournoud: Schema descriptions are translated in 6, so please do not hijack this existing issue for another suggestion.

#332123: Remove t() from all schema descriptions is now in core. This is fixed. For further problems, open new issues please.