Combination View Flat View Tree View
toggle
David H Nebinger
I18N Requirements...
April 1, 2013 1:06 PM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7152

Join Date: September 1, 2006

Recent Posts

So I'm working on building my first portlet to be deployed to the marketplace and have a question about i18n...

First I'm assuming that i18n is required for portlets in the marketplace. Is that assumption valid?

Regardless, I plan on supporting i18n anyway, but I really only speak one language. Using the SDK I can define my language.properties file and the build process will create all of the other message bundle files for other languages. I've created and assigned my microsoft translation id/code so some translation was done during the build, but honestly I cannot verify if the translations are accurate or not (some are not translated at all).

So, when I submit the portlet, how will this quasi-i18n support affect my submission? Is it enough that i18n is supported and left to end users to handle the translation, or will my submission get rejected w/o having actual translations in place?
Corné Aussems
RE: I18N Requirements...
April 1, 2013 1:30 PM
Answer

Corné Aussems

Rank: Liferay Legend

Posts: 1270

Join Date: October 3, 2006

Recent Posts

Hi David,

I do not think it is obligatory to internationalize your Plugins.
Ours are only in English and Dutch (and already some member put in his Spanish translation).
I strongly advise you not to autotranslate. If you need translations pick them from pootle(translate.liferay.com)

It would be great for developers to get their plugins translated in all other languages supported by Liferay.
But honestly, saying this as a translation leader, translating all would become an unachievable task.
Even so it would be great if we could add them to translation process or you open up your git and receive pull requests.
David H Nebinger
RE: I18N Requirements...
April 1, 2013 1:46 PM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7152

Join Date: September 1, 2006

Recent Posts

Well, pootle is not really an option because most of my stuff is very custom (Vaadin-related).

I think supporting i18n is a good thing, especially for a portlet going to the marketplace. I know I'll only ever use the English version, but obviously I can't say everyone would.

I get what you're saying about auto-translating, because what I've been able to reverse using Google translation tools doesn't look right a lot of the time.

I think the git path works, but only for free marketplace submissions... I'm thinking about holding onto this until non-free plugins are supported in the marketplace (don't expect to charge much, like maybe $5 or $10, just something to pay for my time creating it and supporting it).

So for a third party marketplace submission, I would be publishing the portlet w/ the English language bundle. Would the expectation be that users submit translations back to me and I incorporate those into a new version back to the marketplace?

Ideally I'd like to be able to offer the portlet for a low cost but somehow offer incentives (half price or a discount or something) or refunds to those that would do the translations, but I don't know if the marketplace would be able to handle such a thing...