cyclos.org

[admin]

Any communication about the Japanese translation.

[mikami]

Hi,

I'm running Cyclos 3.0.8 in standalone mode, using MySQL.
Both MySQL and Cyclos itself are set to UTF-8.

To prevent Japanese characters (UTF-8) from getting garbled, I had to define charset at the head of some jsp files.
(Or, is this a Jetty-specific problem?)

In all the help files and static files, I added:

[hugo]

Hi Mikami,

It is better not to remove the "escapeHTML" tag because that might cause the layout to break.
It is hard to see what is going on. Could you send the database to ccsoftware@strohalm.nl ? Then we can have a better look.

Regards, Hugo

[mikami]

Hi Hugo,

Thank you for your response.
I have just sent the sql file to you.

I tried with escapeHTML tag on several models of Japanese mobile phones,
but those two pages didn't show Japanese text (nor any text).
Via PC's web browser, I could see the text without problems, though.

Please let me know if you need more information.


Regards,
Mikami

[hugo]

We got your mail. We will have a look and come back to you soon.

Hugo

[hugo]

Hi Mikami,

We loaded your database and application properties. It shows well. Even without defining utf-8 in the static files and helps. I don't know why it works for us.
Anyway I don't think that there will be an simplier way to do it than you did now. I suggest you do the changes from the customization function. This way your changes will stay in the database and it won't cause any issues if you need to upgrade to a newer version.

Regards, Hugo

[mikami]

Hi Hugo,

Thank you for your advice.

I tested with mobile phones of another carrier (KDDI), and they showed Japanese well even with the "escapeHTML" tag.
After all, the problem seems to be due to the particular browser of NTT Docomo, the Japanese largest mobile phone carrier.

Apart from this, I have not yet identified the cause of Japanese static and help files getting garbled.
On your advice, I will define UTF-8 from the customization function after I finish the translation on the text editor.

Regards,
Mikami

[hugo]

Hi Mikami,

Ok, For us it is hard to see if static files are garbeld or not with the Japanese characters. If your work around works fine I suggest you work from that. If you really have a problem we might have to compare the screanshots.

Just let me know if you need more help.

Regards, Hugo

[mikami]

Hi Hugo,

I have just finished all the translation work and sent you the properties, help and static files by e-mail.
Those files are without UTF-8 definition.
It would be very helpful if you would check whether they show Japanese well.
(I also attached my screenshots so that you can check it.)
If so, I might have some sort of character encoding problems outside Cyclos.

And now, I have some questions.

• Could you upload my translation files to sourceforge or the project site to make them available to other users?
  
• Does the translation for Cyclos 3.0.8 have some compatibility with Cyclos 3.5 or later?

Regards,
Mikami

[hugo]

Hi mikami,

I received the files. If you can send the setup properties we will include it in cyclos3.0.9.

Now the bad news.

Cyclos 3.0 does not have compatibility with Cyclos 3.5. This was a difficult desicion. The motive is explained at the project site (copied here below)

Regards, Hugo

In Cyclos 3.5 all help files have been reassembled by main subjects (e.g. payments, references, advertisements, account management, etc). There are a total of 32 help files with a fixed format. The working will be much the same as before. Users can click on the help icons on the funcion windows that will open the help file in a pop-up window and jump to the paragraph of the specific function.
The manuals will be constructed automaticaly from the help files. This way it will be considerably easier for the translators and also easier to maintain the translation. With every release we will publish a 'difference' file that shows (in different colors) all new and modified texts.

[mikami]

Hi Hugo,

I've sent you the setup properties.
Having translated all the help files, I agree that reassembling them is good idea.

Thank you again for your kind assistance.
I'm looking forward to Cyclos 3.0.9 and 3.5.

Regards,
Mikami

[hugo]

We uploaded the version 3.0.9 with the Japanese translation files

First you have to create the new database (mysql) with the utf argument:
create database cyclos default charset utf8;

Then in Cyclos properties you have to set the locale to:
cyclos.embedded.locale = ja_JP

And change the database encoding to:
#hibernate.connection.url = jdbc:mysql://localhost/cyclos?useUnicode=true&characterEncoding=utf8

From version 3.5 Cyclos will support only UTF8 what will solve these kind of language problems.

Regards, Hugo

[mikami]

Hi,

When Cyclos 3.0.9 is set to Japanese in the local settings,
upgrading it to version 3.5 causes a problem.
It seems to fail to configure the accessible channel setting for members,
and all the members (not admins) become unable to login.
(Going to Menu->Permission Groups->Modify member group->Access settings,
there appear no items in the 'Accessible channels' and 'Default channels' drop-down boxes.)
I could avoid this problem by setting language to English before upgrading.

This is because version 3.0.9 has Japanese and version 3.5 does not, isn't it?
Now I'm working on Japanese translation of version 3.5_RC1,
and the application properties file is almost finished.
Where can I find CyclosSetup.properties?
(not found in the Sourceforge packages)

Regards,
Mikami

[hugo]

Hi Mikami,

Good news that you are translation cyclos3.5

[mikami]

Hi,

I found a slight problem in Cyclos 3.5.4.
In "Translation - Notifications" setting, the item "PIN blocked by invalid trials" does not reflect the translations well.
The setting name is shown in Japanese (or in any other language), but Subject, Body and SMS Message remain in English.
They seem to certainly have the corresponding keys in the properties file, so I don't know why.

Regards,
Mikami