Have someone thought about daily re-reading strings from DEV releases?

If I'm looking back how long it have taken to translate big projects like CCK, Views, OG, Panels, Project, etc - I think we should be able to re-import DEV releases every day or we are not able to have a translation ready for final!? CCK have had some RC's, but other modules may not. I'm not sure if it's a good idea to re-read DEV releases, but it could be better to have the translation ready for final and this would at least require a release today - before final or we will not have a translation ready. Not many maintainers care about string freeze and many smaller modules are not releasing RC's... otherwise it would create many garbage and we don't like to keep dead DEV strings or translate garbage... maybe a stupid idea...

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (works as designed)

Yeah, it would create lots of garbage. Basically, we will try and educate people to do RC releases, and get them to understand that they'd only get translations, if they also do string freeze. Working on translations of dev releases for modules, where there was no string freeze is likely problematic as well, since the strings could change anytime. Careless maintainers will do that. So while it sounds like a waste of computer resources, it might also very well be a waste of translator resources. People should rather work on translating stable stuff IMHO.

Because l10n_server will be set up with project module on d.o, we can add a "string freeze" flag to releases which would tell that translators that a release is ready for translation. This flag will probably be named "make available for translation" and would be checked by default on stable and RC releases. Then l10n_server will parse releases which were "made available to it". I think this helps project maintainers tell l10n_server that a release is (almost) ready for translation, and help conserve human and machine resources alike.

hass’s picture

hass commented

"string freeze flag" sounds very nice... however it could take weeks if not months to get a translation ready :-(

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Well, one of the advancements of not using CVS but using l10n_server is that translator teams can work on translations and still distribute them once the module release is out. While with the CVS based system, the translation is only released again, if a new module release is out.

hass’s picture

hass commented

Yes I know... but it would be nice to have the translations ready on the release day... :-)

pvasili’s picture

pvasili commented

I think garbage strings can be simply removed.
The strings can be removed if it is not in any modules (which are now available on the l10_server)