Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 12 of 12

Thread: OpenViX French translation

  1. #1

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts

    OpenViX French translation

    Hi,

    Please find here the french translation for OpenViX.
    Fully translated please trunk it.

    Regards,

    Pr2
    Attached Files Attached Files

  2. The Following User Says Thank You to pr2 For This Useful Post:

    Rob van der Does (18-10-15)

  3. #2
    Rob van der Does's Avatar
    Title
    ViX Beta Tester
    Join Date
    Apr 2010
    Location
    The Netherlands & France
    Posts
    36,247
    Thanks
    1,717
    Thanked 9,461 Times in 6,675 Posts
    Thanks, should be in build 014.

    Help asked via PM will be ignored.
    The forum is there for help and all will benefit from your questions.
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN, IN OPEN FORUM OR PM !

    English is not my native tongue.
    I apologise for all my grammar, spelling and idiom errors.

  4. #3

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    Hi,

    Here is the latest french translation.

    Pr2
    Attached Files Attached Files

  5. The Following User Says Thank You to pr2 For This Useful Post:

    Rob van der Does (31-10-15)

  6. #4
    Rob van der Does's Avatar
    Title
    ViX Beta Tester
    Join Date
    Apr 2010
    Location
    The Netherlands & France
    Posts
    36,247
    Thanks
    1,717
    Thanked 9,461 Times in 6,675 Posts
    Thanks, should be in next build.

    Help asked via PM will be ignored.
    The forum is there for help and all will benefit from your questions.
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN, IN OPEN FORUM OR PM !

    English is not my native tongue.
    I apologise for all my grammar, spelling and idiom errors.

  7. #5

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    Hi,

    Why the fr.po file is not trunked here?

    https://github.com/OpenViX/enigma2/tree/master/po

    Is it the right github to use?

    Pr2
    Last edited by pr2; 02-11-15 at 16:38.

  8. #6
    Rob van der Does's Avatar
    Title
    ViX Beta Tester
    Join Date
    Apr 2010
    Location
    The Netherlands & France
    Posts
    36,247
    Thanks
    1,717
    Thanked 9,461 Times in 6,675 Posts
    We always commit to the dev-branch; we build our test images from there and when we're happy we merge the dev-branch into the master branch.

    I hope you read our 'how-to' and grab the po-file from your box?

    Help asked via PM will be ignored.
    The forum is there for help and all will benefit from your questions.
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN, IN OPEN FORUM OR PM !

    English is not my native tongue.
    I apologise for all my grammar, spelling and idiom errors.

  9. #7

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    Hi,

    Thanks I saw it now, here is the translation for the DEV branch of OpenVIX. So the new strings of the DEV branch are already included.

    Pr2
    Attached Files Attached Files

  10. The Following User Says Thank You to pr2 For This Useful Post:

    Rob van der Does (03-11-15)

  11. #8

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    Hi,

    Can you please approuve this PR, it is the french update from 2018-07-29:

    https://github.com/OpenViX/enigma2/pull/280

    Thanks,

    Pr2

  12. #9
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,317
    Thanks
    6,411
    Thanked 9,142 Times in 6,220 Posts
    How is the script used?

    Edit:
    We also prefer changes to Dev branch. They will get merged into master when a release build is run.

  13. #10

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    Hi,

    Ok new PR created:

    https://github.com/OpenViX/enigma2/pull/281

    For the script it is easy:

    # Pre-requisite:
    # The following tools must be installed on your system and accessible from path
    # gawk, find, xgettext, gsed, python, msguniq, msgmerge, msgattrib, msgfmt, msginit
    #
    # Run this script from within the po folder.

    Once the pre-requisite are met you can easily update all the po files (for exemple I run it on OSX), these ease translator life because now they can update the po file when they want to have them update without having to wait for someone to update them all or to have a fresh enigma2.pot file provided.

    Edit: this also means that translators no longer need to have a full build environment setup on there PC ;-)

    Pr2
    Last edited by pr2; 30-07-18 at 13:32.

  14. #11

    Title
    Junior Member
    Join Date
    Jan 2012
    Posts
    10
    Thanks
    2
    Thanked 6 Times in 4 Posts
    I saw that the script has open a debate on github, I will also cut and paste the answer here because I guess that this will better explain and script and have a better visibility:

    Let me explain:

    The normal build process generates an updated version of the po files but those file are not sent back to github. If I look at OpenViX 'dev' branch I saw that your .po files are 1 year old and I am quite sure that they are new or changed strings in the source code in between that needs translation.
    So your build process generate locally the updated po files but they are not sent back to github (git add / commit / push).

    Before, for a translator if he wants to have the very latest po file to work on, he needs to have a full linux system with a complete enigma2 build environment, then run the whole building process just to have the po files updated locally.

    Today with my script if the following pre-requisite are met (they are mentionned in the script):

    Pre-requisite:
    The following tools must be installed on your system and accessible from path
    gawk, find, xgettext, gsed, python, msguniq, msgmerge, msgattrib, msgfmt, msginit

    Run this script from within the po folder.


    Then it is possible to update the po files on any local PC. I run this script it myself on OSX without having a full build enigma2 environment.

    I know how hard it is to find translators so I try to make something more simple and universal to help them generate the po file they want to work on.

    This script doesn't interfered with the normal build process, he just apply the same logic.
    The script neither include the git command to update the repository, even if they are really easy to integrate.

    As you have already mentioned I have done the same for several plugins repositories (with an adapted version of the script of course) but keeping the same logic.

    So the final goal I try to achieve is:

    to ease translator life
    have the same approach on every repository (enigma2 or plugins) to generate the po files same script name to achieve the same things.
    try to have more translating the images and plugins in there native languages
    If OpenViX doesn't want to have the script in there tree, no problem for me, simply delete it.
    Or if you want to improve it or customised it for your own use please do it.
    If you want to remove my pseudo from it, you can, I am not looking at any glory by providing it. ;-)

    Pr2

  15. #12

    Title
    Member
    Join Date
    Jun 2015
    Posts
    50
    Thanks
    4
    Thanked 13 Times in 9 Posts
    Quote Originally Posted by pr2 View Post

    Before, for a translator if he wants to have the very latest po file to work on, he needs to have a full linux system with a complete enigma2 build environment, then run the whole building process just to have the po files updated locally.
    Interesting approach. Personally, I like to do my translations from the latest image. I update the image to my receiver, download plugin with the .po -file I want to translate, and fetch that one file from receiver to PC that I want to start working on. Actual translation is done by using POEdit.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.