RE: Translations work system

2010-12-07T08:24:32Z

Great news guys and many thanks to Milan.

BTW currently we (me and my wife, a Dutch Literature Msc and editor/lecturer) are reviewing the complete translations.
She really doing a great job in simplifying the techy stuff and makes it all readable for 'normal' people.

I hope we finish before the next EE release.

When finished i'm happy to participate in the Pootle project.

RE: Translations work system

2010-12-07T06:46:40Z

Hi Corné!

Milan is being really pushing for this, and he has even created some scripts for using pootle in Liferay.

I should be reviewing all this with Brian Chan this week so we may have a prototype very soon........

RE: Translations work system

2010-12-04T12:47:28Z

Hi Julio,

It has been quiet for sometime now.
Any updates on the Pootle test?

RE: Translations work system

2010-09-29T22:30:06Z

Attached is the properly displayed social networking portlet menu in Japanese. It seems portlet.xml requires <resource-bundle>content.Language</resource-bundle> even when resource bundle is not used.

RE: Translations work system

2010-09-29T22:23:41Z

Borxa Varela Bouzas:

Why the file begin with

?

I think if the file was created with UTF-8, special characters are represented by 2 bytes, but if the file encoding is set to "Shift_JIS" ... the editor will read the 2 bytes in UTF-8 and it not know what to do in "Shift_JIS".

When you save it, characters stay permanently corrupt, and I see this <title>�T�v</title>, with any solution. (you can see how i copy and paste and characters remain corrupt)

As I have shown in a screen shot in my earlier post on this thread, Liferay's xml parser will not correctly parse when encoding="UTF-8". It seems Liferay's xml parser is only able to parse 1 byte character when encoding="UTF-8". 2 byte characters are all dropped - thus they do not appear on the page.

Characters are not permanently corrupt with Shift-JIS encoding. You're environment probably just do not have the Japanese fonts to display Japanese characters.

In all, I am able to correctly display menu items in Japanese only when file encoding is in Shift-JIS.

RE: Translations work system

2010-09-29T08:25:15Z

Why the file begin with

<!--?xml version="1.0" encoding="Shift_JIS"?-->

?

I think if the file was created with UTF-8, special characters are represented by 2 bytes, but if the file encoding is set to "Shift_JIS" ... the editor will read the 2 bytes in UTF-8 and it not know what to do in "Shift_JIS".

When you save it, characters stay permanently corrupt, and I see this <title>�T�v</title>, with any solution. (you can see how i copy and paste and characters remain corrupt)

RE: Translations work system

2010-09-29T02:44:15Z

Sorry, attached the file in the wrong folder. Attached in the correct one which I created using standard MS Windows Notepad bundled with Japanese version of MS Windows XP.

RE: Translations work system

2010-09-28T08:58:32Z

If you are using Netbeans editor (like me), your problem could be this:

http://forums.netbeans.org/ptopic5782.html
http://netbeans.org/bugzilla/show_bug.cgi?id=75906

Attached is a screenshot with the problem that I could not solve.

RE: Translations work system

2010-09-28T07:56:29Z

Hi Hitoshi,

it seems that the editor you are using is not working fine with UTF-8 because I can't see normally the files that you attached, which editor are you using? have you set your editor to use UTF-8?

RE: Translations work system

2010-09-24T04:41:42Z

It seems Liferay is sometimes unable to handle files which are actually in UTF-8 encoding.

Just putting setting encoding=UTF-8 does not make the file encoding UTF-8.

RE: Translations work system

2010-09-20T10:15:13Z

Great news! ;o)

RE: Translations work system

2010-09-20T10:04:32Z

Hi guys, we finally have Pootle installed in our servers (thanks to Brian Chan!)

We are going to test how it goes. We are thinking of using a plugin as a starting point to evaluate how it works. If it works fine, we will use the tool for the portal later. We will let you all know how to participate in this test as we have it ready.

Thanks everyone (and specially Milan) for your help!

RE: Translations work system

2010-09-17T16:21:29Z

I'm definitely going to take a closer look at the portlet.xml issue, because that is important for translation purposes.

I'll post the results of my endeavours later

RE: Translations work system

2010-09-17T03:00:08Z

Milan Jaroš:

Liferay deals with translation text in a non-standard way, and thus requires a slightly different approach.

I'm not sure what exactly do you mean?

I think Jonathon means Mozilla and OpenOffice did not use automatic translation and used more in a waterfall development model. It's more of first create a stable version, gather people to translate, translate within a set period of time, bundle and release.

Liferay still is suffering some many strings which are not externalized, with properties files which are not placed in a folder in consistent way, properties files with different encoding. Unless these problems are resolved beforehand, messages will be jumping from one file to another and it will be a pain in the neck trying to find corresponding page with the keyword.

I'm attaching a file and a screen shot of social portlet which doesn't handle UTF-8 portlet.xml file too well.(File name of the screen shot represents encoding of portlet.xml)

RE: Translations work system

2010-09-09T14:47:23Z

Sorry, I said we were going to install it in a windows machine but I was wrong... we only have centos as you said

RE: Translations work system

2010-09-09T09:43:15Z

Okay. I have tested it locally and it was looking fine from my point of view. But if you think this would not be helpful for the future localisation management I can reconcile with this.

RE: Translations work system

2010-09-09T09:36:15Z

Liferay deals with translation text in a non-standard way, and thus requires a slightly different approach.

I'm not sure what exactly do you mean?

RE: Translations work system

2010-09-09T09:29:36Z

Hi,
thank you for your involvement. I have posted info about RPMs ahead, maybe this can be helpful for Julio.

There is also that hosting option. But it is not officially supported. As Dwayne told me, they don't have any procedure for that. He is developer who react for my annoying spamming on their IRC channel and mailing-list. ;) I told him some basic info about Liferay and he agreed that they can host our project.

I really don't know Pootle well. I heard about it in this thread first time. I was just interested and involved. There are many thousands of hours of development behind Pootle, I don't think it will be easy to develop something like this from the scratch. AFAIK they have developed many helpful mechanisms to support translators. IMHO we can integrate some parts like dashboard or something easy but not all functionalities.

I personally vote for the Pootle installation (like we are using Jira, Subversion, FishEye...)

According to security:
If we will have own Pootle installed security will depends on Django (Python framework). I really don't know nothing about Python. I just trust.
If we will use hosted solution there is possible abuse of SVN account (with write access to translation folder). But this is not dangerous how it could look like because everything is versioned an you can do roll-back if you wish.
It is similar principle like wiki's or launchpad (I was translating Ubuntu in past ;)) or forums. Everyone can harm by filling in bad words. You just need moderators...

RE: Translations work system

2010-09-09T09:14:25Z

Hi Milan,

we are trying to install pootle in a windows machine in our servers rack. We are not sure if it will fit all our needs, we might develop our own tool... but I will reach you if we find any problem about it and I will try to keep all the translators in the loop.

Thanks a lot!

RE: Translations work system

2010-09-09T08:53:03Z

Hi Julio,
I am not sure what is the preference of Liferay. It is possible to have hosted solution on http://pootle.locamotion.org/ or we can install it.
I can help you with the second solution. AFAIK you are using CentOS which is based on RPM. I have found list of supported distro's but I'm not sure about compatibility.

Regards,
Milan