About translations

Hello UNA team,
The current method for creating a translation package has some difficulties which may block people to do translations of UNA:

  1. The translator needs to have enough GNU/Linux skills. As  it is needed a good language knowledge and GNU/Linux skills at the same time, this limits the number of possible candidates who can do the translation.
  2. In the explanations in Creating a Language pack there are still confusing unclear parts.
  3. With the current method it is very likely to do errors in the language files codes, and these are difficult to find after.
  4. Polyglot is very nice for translations but we are not very informed about it's functions like where it is recording the edits, to the module language files directly or keeping in the database? When with developer we recomply what it is doing, when we restore what is it doing? ( the details like where it is reading/writing the data)
  5. After translating the language files we are doing many edits through polyglot and as explained in paragraph 4, we dont know if these edits are sysncronised with the translation fIles. In a previous post Alex explained 4 & 5 .
  6. For a full translation we need to have the module files of the modules we didn't buy. Yes may be we may download them from GIThub, but this is another + procedure to do.
    As a result in current state to do a translation is torture and consuming a lot of time.
     My recommendation is to develop a method to create a new language just through the nice Polyglot interface and when it finishes download /send the files of the module from Polyglot with one click.

    Current method creates barriers for translations, UNA team may consider simplifying it.
    Dear UNA team what are your opinions please?
  • View
    182
  • More
Replies (13)

    • Thank you for these points, we'll consider it for the future:

      https://github.com/unaio/una/issues/1633

      For a while could you please clarify point 2, which paragraph/sentence of the documentation is confusing ?

      • Thanks Alex for listening our ideas. 

        I will write the confusing points there until the end of this weekend.

        • Thx Cem! That would be real useful to manage the creation of new languages in studio/polyglot.

          For my needs a default 'language english container' would be great. I could save it under the name of the language I need and could translate the real necessary keys for my users. 

          Translation of the admin keys could be kept in english and translation of the public/user keys could be done as needed.

          • yes Peter admin and user interfaces to be two different translation jobs. I am sure many people will prefer not to translate the admin interface.
            But if it is possible I dont know.

            • Just imagine the fun and convenience for users, if the site offers 'regional dialect' language options to choose... in the german language area I'm talking about dozens of dialects. That would be - think marketing and cr - just great *g

              btw, it would be one of the unique assets of UNA, the ''simple translator''

              • Now there are only 4 languages translated English French German and Russian with 1000 real subscriptions this is nothing. 

                At least it was to be more then 10 languages till now. 9 + versions passed.
                but the current procedure is really difficult and needs your own server to proceed (let`s say) easier.
                I guess this is the barrier. If UNA does a web interface to create language modules through Polyglot/studio I am sure many new languages will appear shortly and this is very important for UNA too.

                I did the Turkish module, there are some little problems I wrote to Alex, lets see.

                • ... and german is not up to date

                  • By the way UNA uses universal language files which are used in Android as well, so some online services can be used to ease the translation, for example this one:

                    https://lokalise.co/

                    • No Alex we will not use them we have the beautiful and extendable program called Polyglot 😇 

                      • Hi Alex about the confusing parts of the language pack creation explanation. My notes, I left at my clinic so tomorrow morning I will be able to write.

                        • Hello Alex about the confusing (at least for new beginners) parts of the language module creation, here are my notes:

                          ....

                          3.  ... classprefix specified in point 1, to be point 2 .
                          4. 

                          • Edit modules/vendor/french/install/langs/en.xml file, by changing only the following:

                            • change all language key prefixes to your own, for example from _bx_rsn_ to _vend_fr_
                              (and we may  here add for the resources line make the changes like rs to fr Russian to French
                              <resources name="ru" flag="ru" title="Russian">
                            • change translations from Russian to 'French`


                          9. To package the module, run the following from your UNA root folder (it requires build.xml file which is in the UNA repository): /path/to/phing package_module -Dvendor=your_vendor_folder_name -Dmodule=your_module_folder_name
                          ZIP file for the module will appear in /packages/ folder in your UNA root directory.

                          * Here shall we copy the xml files that we translated from:
                          packages/en  to >>>>>      modules/vendor/french/data/lang/bx_albums
                          or the packing script does this?
                          * When we want to test installation of our pack, shall we first delete/rename the modules/vendor/ourlanguage directory to simulate someone who never ınstalled our language pack? If we dont delete / rename this directory can we install  the lang pack?
                          8. When new version of UNA is released you need to update module and add/remove/change some language keys. The list of changed language keys can be found in English module update files, also you can also use it as a template to create own language module update. For example the here is the list of changes from 9.0.0 to 9.0.1 for English language.
                          I found the update file and there are add and del commands in the xml file that shows me that the update script will work on this xml .  And there are same type of update files for the other modules.
                          I thing we need to create copies of these update files and translate them for instance
                          For English language:
                          /modules/boonex/english/updates/9.0.9_9.0.10/install/langs/en.xml    >> fr.xml
                          For albums module
                          una/modules/boonex/albums/updates/9.0.9_9.0.10/install/langs/en.xml    >> fr.xml
                          After that what to do? We will leave the new files there and when the users updates their modules will they automatically used?
                          We need detailed explanation about the update procedure here.

                          • Thank you for your points I've changed 3, 4, 8, 9 points in the documentation:

                            https://github.com/unaio/una/wiki/Creating-new-language-module

                            • Thank you Alex
                              Login or Join to comment.