OLD-6615: Non-English Language files need updating

[cpaschen]

Description

Most of the non-english language files are missing a LOT of the latest updates to the english language file.

Add the missing sections (NOTE: Translation will still need to be done by volunteers, but just copying the english there will make this much Quicker!)

History

#11 Updated by Chris DioscouriChris Paschen. 5 months ago

Target version changed from Version 0.9.1 - EAV (Custom Fields) Finalization to Version 0.9.2 - POS Finalization

I'm moving this to 0.9.2 because we really need to get 0.9.1 out there with all the language changes; have some time to fix any missed strings/translations; and then release the new language 'package' model for users to use when translating.

There's really nothing left to do on this other than to run the build when the language files are close to stable (which they are NOT necessarily with the 0.9.1 release).

#10 Updated by Chris DioscouriChris Paschen. 8 months ago

Target version changed from Version 0.9.0 - Major Core Fixes to Version 0.9.1 - EAV (Custom Fields) Finalization

#9 Updated by Chris DioscouriChris Paschen. 8 months ago

Target version changed from Translations to Version 0.9.0 - Major Core Fixes

I'm moving this into the 0.9.0 core.

Mainly so that this gets documented and so that translation into other languages can be updated.

NOTE: If this ends up holding up 0.9.0 ... we might move it to 0.9.1 (or even create a 'mid-version' release just for language translators).

#8 Updated by Chris DioscouriChris Paschen. 9 months ago

Status changed from Requires Feedback to In Progress

OK ... I'm going to let this sit for now.

When we actually 'deprecate' the old language files, we'll move this into a specific version (so that it shows on the changelogs properly]

Also, this will require a blog post of it's own - to explain our new 'base language package' concept and ask for translators.

I'm going to do the same thing on the other extensions so that translators can work on multiple extensions if they would like.

(I'd still like to get the Tienda base package out with 0.8.3 - possibly even before it is out in a stable version.)

#7 Updated by Lukas Polak 9 months ago

Target version changed from Version 0.9.0 - Major Core Fixes to Translations

I second Chris idea. It's rather time-consuming for us to convert all language files and this might be a great place for the community to step in (so we could focus on more important tasks). Creating a base package should be really helpful for them. Therefore, we should consider language packages which are older than version 0.7.0 as depreciated. That's my humble opinion.

Lukas

#6 Updated by Chris DioscouriChris Paschen. 9 months ago

Thanks - I hope others will do the same.
The language files are WAY too old now, so we need a way to make this process easier.

Please do jump in with comments as I get this project working. I want to make sure that we can make this work easily for everyone.

Also ... we're working on language file 'updates' that would, in effect, make all the files broken for the 1.0 release. That is, in part, due to preparing Tienda for J2.5. The language files are one of the biggest roadblocks to that upgrade. But considering they are almost all so old, I think it would be faster to just start from scratch -BUT with a base that is much easier to translate.

So, before anyone goes and complains about the process ... be warned, in advance, that this will happen.

#5 Updated by Vincent L. 9 months ago

Excellent idea Chris :)
Once this 'base language' package is finished, I will finally be able to update the Dutch translation to be Tienda 8.3 compatible >

#4 Updated by Chris DioscouriChris Paschen. 9 months ago

Can anyone explain how the 'build languages' routine works in the ant package?

Would it be possible to just create a 'build base language' option in ant, that would just find all language (i.e. 'ini' files) and put them all in the proper package structure for a language package)?

#3 Updated by Chris DioscouriChris Paschen. 9 months ago

Status changed from Closed to Requires Feedback

After trying to resolve another user issue - it turned to be problems with a language file that was done wrong (missing entries, wrong entries, duplicate entries), I think we need to focus some attention to the language files.

Here's what I am proposing that we do:

1. Plan that all the language files will be dumped for the 1.0 stable release.
   More than 1/2 the files haven't been updated since 5.0.x, so they don't have 1/2 of the phrases translated anyway.
   NOTE: We won't actually delete them, but just consider them OLD - but let users use them as reference for new translations if they would like.
2. Create a new 'base language' package. (See #6618)
   This would be a package (that is kept current, along with the english files) that is based on english, but is a zip file (like an installer). This will allow novice (technically) users to more easily translate the language files (and give us a 'benchmark' for the following step).
3. Comparison check new translations
   When new translations are provided, do a basic file comparison on the files (between the translated file and the base file). If the translation provided doesn't translate the complete file, all of the files (in the package) or has somehow changed or added to the file structure - the translation would be sent back to the user for fixing.

I think this will help adoption of Tienda by more users if we have these language files. And doing this will help translators do the work more quickly.

The only task will be to ensure that when the English files are updated that the 'base' files are updated.
This should be easy for the main language files (just update upon release), and it should be relatively easy to

#2 Updated by Chris DioscouriChris Paschen. 9 months ago

Status changed from New to Closed
Resolution set to Fixed

All the present main language files have been updated (module/plugin files have NOT been updated yet).

#1 Updated by Chris DioscouriChris Paschen. 9 months ago

Subject changed from Non-English Language files are WAY behind to Non-English Language files need updating

Associated revisions

Revision 2365

Added by Chris DioscouriChris Paschen. 9 months ago

Fixing wrong french language strings refs #6615

Revision 2361

Added by Chris DioscouriChris Paschen. 9 months ago

fixing main language files in translations fixes #6615

[rdiaztushman]

CP, could you take care of the process of copying over the missing sections and renaming the constants so they match what is in use in the English files?