A lot of translation effort seems to happen in Cyn.in 3.1 and I've tried a bit with Thai translation. As a Thai, I found that a lot of translations are not quite correct and the all the thing is just a beginning (a lot to be done). If I can be of some hel

Dhiraj Gupta — Thu, 04 Feb 2010 22:09:42 +0000

Thanks for pointing out the fix suiato, the same has been now committed to Cyn.in core svn trunk, and it should work for all languages.

A lot of translation effort seems to happen in Cyn.in 3.1 and I've tried a bit with Thai translation. As a Thai, I found that a lot of translations are not quite correct and the all the thing is just a beginning (a lot to be done). If I can be of some hel

Chairat Siripatana — Thu, 04 Feb 2010 22:09:41 +0000

A lot of translation effort seems to happen in Cyn.in 3.1 and I've tried a bit with Thai translation. As a Thai, I found that a lot of translations are not quite correct and the all the thing is just a beginning (a lot to be done). If I can be of some help please inform me. I myself need Thai translation in a few community engagement web-sites if Cyn.in is to be used.

Steven Lai — Wed, 03 Feb 2010 17:05:20 +0000

Great job ! Suiato , it could be hard and take time to find the bug. Hope new translator can avoid this pain by reading your solution , thank Dhiraj , too.

In Chinese version , there is also this problem , activation mail should show a URL to user but it just been put SET_PASSWORD string there , if I changed UI back to English at the 1st moment , then send out the activation mail , it will not send the wrong string .

ToshiTeru HOMMA — Wed, 13 Jan 2010 15:08:58 +0000

Thanks, Dhiraj

I was struggling, and found a fix: change i18n:name="reset_url" to i18n:name="set_password" in /src/ubify.cyninv2theme/ubify/cyninv2theme/skins/ubify_cyninv2theme_custom_templates/registered_notify_template.pt . That's it :) Deadly simple, but took a long time for me to figure out :-(

As passwordresettool.pot shows that msgid "mailtemplate_registered_user_body" is at PasswordResetTool/skins/PasswordReset/registered_notify_template.pt, I was looking at the template file and found nothing wrong with using the variable ${set_password}. After a long painful time of struggle, I've found there are two files named registered_notify_template.pt (!) and the customized one at /src/ubify.cyninv2theme/ubify/cyninv2theme/skins/ubify_cyninv2theme_custom_templates is used in practice. I think it happened when registered_notify_template.pt was customised for HTML version and somehow ${set_pasword} was changed to ${reset_url}.

This was a bug easy to fix once the customization was known. Learned again finding what's done in reverse process is hard and painful.

--
Teru

Dhiraj Gupta — Tue, 12 Jan 2010 21:27:08 +0000

Created issue for tracking this - it's important and will be fixed soon. Here: http://odn.cynapse.com/issues/1273

Thanks for pointing this one out, suiato

ToshiTeru HOMMA — Sun, 10 Jan 2010 22:40:45 +0000

Sorry, but i have to take my words back. When i reinstalled cyn.in while OS is running python 2.4, the problem of ${set_password} showing up in the email a user receives reappeared. Now i noticed no syntax errors of return etc., but, i still get this. It works fine in English locale, but happens in other locales.

Maybe i should give up running the trunk version...
i'm hoping to create a community site using cyn.in, but starting to realize it's difficult with my limited knowledge and without support.

i'll appreciate help.

--
Teru

ToshiTeru HOMMA — Sat, 09 Jan 2010 04:56:09 +0000

Thinking back, I'd casually presumed cyn.in/plone/zope were running in a virtual envirionment. But, what turned out was that /usr/bin/python was running to execute the command in templates. Did I miss something or some setup to make it run python in the virtual envirionment?
--
Teru

ToshiTeru HOMMA — Sat, 09 Jan 2010 01:53:34 +0000

I found what caused the problem. My OS was running Python2.6 while cyn.in was built with Python2.4. Linked /usr/bin/python to python2.4, and that solved the problem :) Sorry it took me some days to figure this out. I'm thankful for this forum and Dhiraj giving me a chance to discuss and think about it.
--
Teru

ToshiTeru HOMMA — Fri, 08 Jan 2010 05:44:32 +0000

Thanks :)

I think cyn.in can be much more popular in Japan once its translation is readily available.
For me, this bug is very strange and difficult to cope with.

Currently, I'm running cyn.in on Ubuntu 9.10 server, and remember some syntax errors about return statements during buildout. Mainly followed the instructions Cyn.in developer guide[1]. When running cyn.in by turning on debugging in zope.conf, I get a lot of warnings on a terminal, which are mainly on deprecated statements. Possibly, they could cause trouble like this one?

This is a little bug, but critical to register users in locales other than English. I will appreciate any advice/pointers/hints.

[1] http://www.cynapse.com/[…]/howto-development-environment-quickstart

--
Teru

Dhiraj Gupta — Thu, 07 Jan 2010 08:27:26 +0000

Cool! Would love it if you'd contribute the Japanese translation once you're done, thanks! :)

Hmm.... we had done something with that password reset template once, I think. This might be screwing things up with the translation.

Will look and update, shortly.

ToshiTeru HOMMA — Thu, 07 Jan 2010 06:26:28 +0000

I'm working on Japanese translation of cyn.in (from svn trunk). Translating cynin-ja.po is mostly done, but I found there are other po files to be updated.

My current problem is in passwordresettool.pot at /eggs/plone.app.locales-3.3.5-py2.4.egg/plone/app/locales/i18n. Specifically, the following part:

#. Default: "Welcome ${fullname}, your user account has been created. Please activate it by visiting ${set_password} You must activate your account within ${expirationtime} hours, so before ${expirationdate}"
#: PasswordResetTool/skins/PasswordReset/registered_notify_template.pt:23
msgid "mailtemplate_registered_user_body"
msgstr ""

When the current Japanese translation passwordresettool-ja.po is used, the user receives an email where ${set_password} is not replaced by the URL for registration, but appears as ${set_password} . The same problem occurs when using other po files such as paswordresettool-it.po. However, when I use English locale, the URL correctly appears in the email message the user receives.

I understand the above part belongs to Plone translation, not cyn.in, but will appreciate any advice or pointer to fix this problem.

--
Teru

Dhiraj Gupta — Sat, 26 Dec 2009 10:23:16 +0000

Cool.

We're looking at doing a quick follow up release with bugfixes and updated translations in early January. We'll include the updated Thai translation in it, thanks! :)

Chairat Siripatana — Fri, 25 Dec 2009 13:24:04 +0000

Thank you very much Dhiraj. It seems simple to start doing Thai translation. I will do it as soon as I finish setting up the public community engagement portal (should be before coming Monday). I will inform you then. For Plone products I am using let me give you a list a few hours after this. I'd like it to be more precise and give the reasons why I am using it. Anyway, I like Cyn.in very much !

Dhiraj Gupta — Thu, 24 Dec 2009 21:40:41 +0000

Yes, it would be great if you could contribute! :)

To do this, all you need to do is open up the cynin-th.po file, (you'll find it in:
<buildout folder>/src/ubify.policy/ubify/policy/i18n/cynin-th.po) with a PO file translation tool. We recommend POEdit (http://www.poedit.net/) if you don't have a preference. Update whatever strings you find missing or wrong, and submit the file to us and we'll include it in an upcoming release. There's a quick bugfix release that's going to happen really soon, so it would be even better if you did a quick pass to fix the glaring or really bad ones first and then did more detailed work where required or on your free schedule.

More formal documentation for translation and languages is being made, it will be put up soon.

It's great that you have found opportunity to use Cyn.in in your community engagement web sites. Do let us know how we can help with this, if you get stuck anywhere. Also, once you have a public or registration site online would be great to see how it looks / works as well. :)

You mention requiring to use some plone products in a normal plone scenario? Please list them if you can, it would let us help you out by at least telling you if we know some / any of them already work or not.