Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author oferwald

    (@oferwald)

    Hi,

    I am not sure that you understand what translate in default language stands for ?? (probably I didn’t explain it well enough)

    It translates in default language only parts that are clearly marked with lang=xx html attribute, and avoids translation of the rest. If you want to get your widgets translated from English you have a few options:
    1. use codestyling localization and transposh .po/.mo integration
    2. wrap the widgets with a <span lang=”en”>

    I hope this helps, always happy to get feedback.

    Thread Starter ChemaZ

    (@chemaz)

    Found this:

    Translation of the default language only works where there are html elements marked with a different language than the default one, what is the point in translating English to English? However – if a user leaves a comment in Spanish, it is marked as such, and when enable default language translation is enabled it will enable the translation of said comment to English.

    So, Transposh currently assumes that the plugins and themes are in the default language, correct? Still, it would be great to be able to Transposh the ones that aren’t.

    Before I go on a code safari, how hard or dangerous could it be to enable Transposh in all the default language pages?

    Plugin Author oferwald

    (@oferwald)

    Hello,

    Did you read my previous answer?

    and yes, it assumes everything is in the default language (unless specified otherwise)

    Thread Starter ChemaZ

    (@chemaz)

    No, I didn’t until now. We must have posted simultaneously, or perhaps I should swap my tea for some coffee. ??

    So I guess I’ll go with CodeStyling Localization, though it’s interface is not as practical as Transposh unless you want to translate everything. On the bright side, it allows for easy translation sharing. Speaking of which, do you have any plans for an export .po feature? Would be easy to implement, and then it would be a snap to make .pos for specific plugins or themes with the aid of msgcat.

    And just so I don’t misunderstand again, what is exactly what “.po/.mo integration” does? It would be nice if you put these explanations in the FAQ or some sort of manual (and if you added it to the backend’s Help).

    Thanks for the prompt answer, and a great plugin!

    Plugin Author oferwald

    (@oferwald)

    Hi again,

    Had no such plans, yet, also – did you consider the lang wrapping?

    Hi,
    Default Language do’nt work. For example in admin side enable default language ‘Deutsch’ but in the fornt end side default language do not change in ‘Deutsch’.
    please help me.

    Plugin Author oferwald

    (@oferwald)

    Hello,

    Next time, please create a new topic and don’t resume a 3 month old resolved topic, but to the issue.

    Default language – sets the language the site is written in, not the default language the site will be displayed in.

    Translate in default language – allows segments written in other languages inside the default site to be translated (example foreign language comments)

    Good luck, and there will be no further replies in this topic

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: Transposh WordPress Translation] default language translation not working’ is closed to new replies.