Translation powered by Transifex.com for MediaPortal 2 and many community plugins (1 Viewer)

[chefkoch]

1. In Transifex when we enter the translation and we need to add the '{0}' things (and other special characters), it looks OK when we enter them. However when I want to see the translations it doesn't look good (i.e. '}0{' ). How do I know if it is written correctly and if it will serve it's purpose?

Good news. Regarding RTL support the Transifex team was really fast. Both issues I added, are fixed and will be live soon.
https://github.com/transifex/transifex/issues/113
https://github.com/transifex/transifex/issues/114

Please give feedback as soon as you'll notice a difference and the change is live.

 

[Kucheek]

Hi all, I joined the Transifex team today to help with the translations (czech language in my case). I want to start with what I feel is most important - to add the commonly used terms into the glossary since I found in past that there was a lot of inconsistency in MP1 in the area of commonly used terms (I translated a couple of plugins for MP1 before).

I have discovered that the glossary already contains certain entries for german language but I feel that the way how the terms have been added was incorrect. The issue is that the keywords are in german and definitions describe the english source strings. Now when you switch to any different language variant of the glossary, you see the keywords still in german and the definition fields are available to be filled with translations / explanations of that selected language variant.

I think it should be exchanged - to place the german terms into definition fields and have the english terms in keywords. Using this approach, all the language variants of glossary will see the english terms and other users contributing to different languages will be able to use the glossary as well.

 

[chefkoch]

Hi all, I joined the Transifex team today to help with the translations (czech language in my case). I want to start with what I feel is most important - to add the commonly used terms into the glossary since I found in past that there was a lot of inconsistency in MP1 in the area of commonly used terms (I translated a couple of plugins for MP1 before).

I have discovered that the glossary already contains certain entries for german language but I feel that the way how the terms have been added was incorrect. The issue is that the keywords are in german and definitions describe the english source strings. Now when you switch to any different language variant of the glossary, you see the keywords still in german and the definition fields are available to be filled with translations / explanations of that selected language variant.

I think it should be exchanged - to place the german terms into definition fields and have the english terms in keywords. Using this approach, all the language variants of glossary will see the english terms and other users contributing to different languages will be able to use the glossary as well.

Good point. Thanks for informing us. I'll take care to fix it asap.

If you would like to make some kind of manual, how to use and work with the glossary, feel free to add information to the wiki

Thanks to all our translators as well for the great progress, which we made the last weeks. Even 3 to 4 new strings are being translated to more than 10 languages within 2 days amazing.

 

[chefkoch]

Ok I created the English terms and copied the German terms to German definition.

It is not possible to delete terms in glossary, yet. Transifex team is working on it and will release a complete reworked glossary next weeks.

 

[chefkoch]

We are preparing a new MP2 test release.

If your language is not finished, yet or does not even exist, create an account @ Transifex.com now and start your translation.
For more infos take a look at our Translation Guide.

 

[chefkoch]

1hour gone. Swedish is finished

 

[velis]

I logged into transifex today to find some new strings to translate. However I find it impossible to do the translation. Anything I try to translate yyields an error "encode() takes no keyword arguments" and refuses to save.
Anyone else having this issue?

 

[chefkoch]

Hi all,

Transifex updated the glossary feature completely. http://blog.transifex.com/2012/07/new-glossary-features/

So for each glossary term (English) we now can add a translation (for each language of course).
A comment/description for each term can be stored in English as well as other languages.
It is also possible to store whether it is a noun, verb etc...

Check it out and increase the quality of MediaPortal 2 translations...

 

[chefkoch]

We are happy to announce that MPExtended joined our TeamMediaPortal project @ Transifex.
More information about MPExtended can be found in it's forum.

MPExtended is using TeamMediaPortal as a project hub, this means all existing language teams are available for MPExtended right from the start.

Feel free to translate MPExtended into all the languages, which are already available for MP2, and even more.

 

[azzuro]

Hi, for user want to translate file in offline mode,
Software For EDIT 1 file .resx:
1. RESX Editor - http://sourceforge.net/projects/resx/

Software For TRANSLATE/EDIT from 2 file .resx:
1. SIMPLE RESX EDITOR - http://code.google.com/p/simpleresxeditor/ (Better because, you can COMPARE files with display in highlight the differences)
2. RESX TRANSLATOR - http://sourceforge.net/projects/resxtranslator

@ubela64 essai de lire le fichier avec ces logiciel.