WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Localization files in /languages folder

[Resolved] Localization files in /languages folder

Viewing 15 replies - 1 through 15 (of 19 total)
  • @vaultdweller,

    Subscribe2 supports placing the language files in the root of the plugin folder, in a languages sub-folder and hopefully, once WordPress allows, in the core languages folder.

    If you are suggesting I add localisation files to the release archive, well I’d love to do that but I get the translation files donated to me sporadically and some of the version I have are very old indeed. Furthermore, I don’t feel it’s right to push a code release that simply contains a new translation file when the core code remains identical.

    Access to all the i18n files that have been submitted to me are available here:
    http://plugins.trac.wordpress.org/browser/subscribe2/i18n

    > I get the translation files donated to me sporadically and some of the version I have are very old indeed.
    That is not a big problem compared to the fact, that users currently are not getting ANY translations! Incomplete translation motivates users to update them!
    That is the way most plugins I use are working!

    > I don’t feel it’s right to push a code release that simply contains a new translation file when the core code remains identical.
    You don’t need to do that. Push new localization updates with new version of software.

    > Access to all the i18n files that have been submitted to me are available here
    I was lucky to find this link as I wanted to start translation from zero!

    You should definitely include all translations to release!
    Besides, moving to GIThub will also be good for development of the project!

    > I don’t feel it’s right to push a code release that simply contains a new translation file when the core code remains identical.
    Besides, you can update release with lang. files without making a new version of it!

    @vaultdweller,

    If I add a new translation file to the current release without bumping the version number how are users going to know there is a new translation file in the updated download archive?

    Old users will know about it only on new release.
    New users will know straight away!

    Not the bet practice, but as translation is not function related it can be sometimes used.

    But if your releases are frequent enough then you don’t need to use this approach. Translation will be included with new version…

    If someone needs latest translation he will install it from your Github.

    @vaultdweller,

    Maybe I’m missing something but I don’t see how your proposal will help end users or me.

    I should include all translations with the code? Even one I know to be broken? That’s just going to result in more support requests saying the translations don’t work.

    I am trying to preserve strings as far as possible between versions but sometimes even point releases contains changed or new strings so adding translations to new code releases is probably going to leave some strings untranslated.

    Clearly you know about *.mo files and the principles of i18n but most people want to install the code, turn it on and have it work without doing anything further.

    > I should include all translations with the code?
    Yes!
    > Even one I know to be broken?
    What does it mean “broken”? If it results in functional problem, then no. If some string are not translated then it is not a big deal. Users might translate it later.
    > so adding translations to new code releases is probably going to leave some strings untranslated.
    No a big deal. Users who need translation will translate!
    > Clearly you know about *.mo files and the principles of i18n but most people want to install the code, turn it on and have it work without doing anything further.
    That is what software needed for!
    See examples how users contribute translation when they need it:
    https://github.com/easydigitaldownloads/Easy-Digital-Downloads/commits/master/languages
    https://github.com/kregwallace/speakup-email-petitions/commits/master/languages

    And many more! That is the way it is working right now!

    > That’s just going to result in more support requests saying the translations don’t work.
    Answer to these request such a way: “I would be glad to include updated translation if you will send me on!”. Do the programming stuff and leave translations to users!

    @vaultdweller,

    Okay, I can understand your arguments but how is GitHub different from Trac and Subsverison now? I get people submitting translation files now:
    http://plugins.trac.wordpress.org/query?component=subscribe2

    What are the benefits (and disadvantages) of moving to git from subversion? Why should I do this before the WordPress core and plugin repositories do the same? (I’m asking in all seriousness here)

    > What are the benefits (and disadvantages) of moving to git from subversion?
    I gave you links to Github just to show examples of localization process.

    Advantage of GitHub over other code hosters is it social attraction for users. GitHub UI is very user friendly.
    I don’t want to start holy war. Just in my opinion GitHub is mainstream currently…
    I personally don’t know even how to contribute to SVN based projects. Somehow it is inconvenient as it lacks UI simplicity…

    @vaultdweller,

    I guess you use the tools you are used to. I’ve always used subversion as that is what WordPress used when I started looking after the Subscribe2 code 6 or 7 years ago.

    I saw the GitHub links but as I don’t use GitHub and am not failiar with it it didn’t mean much to me. So, can people just commit changes to the code? Is that how it becomes ‘social’? If that can commit changes for languages how do I retain control over the core code?

    Well, I was not insisting on using Github.
    I just gave you examples, where users were shown contributing Lang files.

    My key point was not to move your development to GitHub, but to ask you to include Lang files in the /languages folders so that users can start using translation right after installation.

    If the Lang file is incomplete then it will motivate users to contribute translations.
    Right now it is not clear for users where and how to add translation!

    @vaultdweller,

    I’ll have a think about what you have suggested. I clearly need to make it easier to find the translation files and direct people to the POT file and the Trac site.

    Wow! Lucky me i found this thread!
    I was starting translate in italian the plugin when i stumble upon a reference to translation, so i came here and discoered that there are the updated italian translations!
    You should tell people in the plugin’s description pager that you (great) plugin support, and has, translations!!!

    [and i agree with @vaultdweller!]

    @eyephone21,

    I prefer the idea of linking to the available translations from the plugin page.

    I’ll see if I can add a link to the plugin page description on the same line where it says “Settings” and “Donate!”, perhaps a link to:
    http://plugins.trac.wordpress.org/browser/subscribe2/i18n/
    Says “Translation Files”.

    Sure, it will be enough!

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘[Resolved] Localization files in /languages folder’ is closed to new replies.