I added a new branch to the repository today named ‘jargon’ and merged
Kieth Bingman’s changes to support Gibberish in from ticket 507
(http://dev.radiantcms.org/radiant/ticket/507).
Jargon needs the following before it can be merged into head:
- A combo box needs to be added to the login screen that will allow you
to select your language
- Support for auto selecting the language based on the content type
requested by the User’s browser
- A strategy that will allow extensions to offer multi-language support
- More language translation files
- More tests
Hopefully this will give us a place to coordinate efforts on
internationalization.
–
John L.
http://wiseheartdesign.com
On Jul 21, 2007, at 5:58 PM, John W. Long wrote:
I added a new branch to the repository today named ‘jargon’ and merged
Kieth Bingman’s changes to support Gibberish in from ticket 507
(http://dev.radiantcms.org/radiant/ticket/507).
Cool! I have discovered a few things missing in that patch this week
and have uploaded the corrections.
Jargon needs the following before it can be merged into head:
- A combo box needs to be added to the login screen that will allow
you
to select your language
Per user languages were something I wanted to add, but I was waiting
to see were you went with this.
- Support for auto selecting the language based on the content type
requested by the User’s browser
I am not quite sure where this would fit in if you can select the
language at login.
- A strategy that will allow extensions to offer multi-language
support
This one is hard. The way Gibberish works is that it loads the
language file. The easy way to do it is too paste the changes onto
the language file, but this will get out of control very quickly.
Ideally an extension will have it’s own Gibberish files. At very
least, each extension that replaces a view needs to be updated to
support Gibberish. Do you have any thoughts about this John?
- More language translation files
I have a German translation done and will submit that as a patch.
Another thing that will be needed is a good way to submit and review
translation files. I am not sure you want patches for every language.
Hopefully this will give us a place to coordinate efforts on
internationalization.
Keith B.
Tel: +49-7731-7983830
[email protected]
http://keithbingman.com
Keith B. wrote:
Cool! I have discovered a few things missing in that patch this week
and have uploaded the corrections.
Can you create a patch for these against the Jargon branch and attach it
to ticket 507?
- A combo box needs to be added to the login screen that will allow
you to select your language
Per user languages were something I wanted to add, but I was waiting
to see were you went with this.
Ok, thinking out loud here. Perhaps it should be configured under
user/preferences instead. That way you wouldn’t have to select it every
time you logged in.
- Support for auto selecting the language based on the content type
requested by the User’s browser
If it hasn’t be configured on the User preferences page, I’d suggest
that we auto-detect it when they log in.
- A strategy that will allow extensions to offer multi-language
support
This one is hard. The way Gibberish works is that it loads the
language file. The easy way to do it is too paste the changes onto
the language file, but this will get out of control very quickly.
Ideally an extension will have it’s own Gibberish files. At very
least, each extension that replaces a view needs to be updated to
support Gibberish. Do you have any thoughts about this John?
I think it’s just a matter of creating a load path for language
translation files so that Gibberish knows to look in multiple places and
can resolve conflicts between files based on load path precedence.
Once that level of support has been added to Gibberish it should be
fairly trivial to ensure that each extension’s translation files are
loaded correctly.
I’m definately open to suggestions here.
–
John L.
http://wiseheartdesign.com
John W. Long wrote:
Wait a minute. I see that you created a new ticket for this:
http://dev.radiantcms.org/radiant/ticket/518
I’ll apply it now.
Done:
http://dev.radiantcms.org/radiant/changeset/466
–
John L.
http://wiseheartdesign.com
Hello!
how do i freeze radiant application to jargon branch?
John W. Long wrote:
Keith B. wrote:
Cool! I have discovered a few things missing in that patch this week
and have uploaded the corrections.
Can you create a patch for these against the Jargon branch and attach it
to ticket 507?
Wait a minute. I see that you created a new ticket for this:
http://dev.radiantcms.org/radiant/ticket/518
I’ll apply it now.
–
John L.
http://wiseheartdesign.com
Keymone wrote:
Hello!
how do i freeze radiant application to jargon branch?
rake radiant:freeze:edge BRANCH=jargon
I’ll be making some changes to the branch today, by the way. I got a
patch to Gibberish accepted that obviates the need for the
extension_languages extension.
Sean
?? wrote:
I have Japanese translation file (ja.yaml) . And I want to submit
this file.
What should I do?
Attach it to a ticket on the Trac site.
–
John L.
http://wiseheartdesign.com
Hello.
I have Japanese translation file (ja.yaml) . And I want to submit
this file.
What should I do?
–
rish(Ryutatsu Ishigami)
[email protected]
[email protected]
Thank you for reply.
I submitted translation file(ja.yaml).
see below.
http://dev.radiantcms.org/radiant/ticket/507
–
rish ( ryutatsu ishigami)
[email protected]
[email protected]
Ryutatsu Ishigami(rish) wrote:
Thank you for reply.
I submitted translation file(ja.yaml).
see below.
http://dev.radiantcms.org/radiant/ticket/507
Committed:
http://dev.radiantcms.org/radiant/changeset/469
–
John L.
http://wiseheartdesign.com
I’ve attached a Dutch translation (nl.yaml) as well.
Perhaps it is wise to maintain a registry for translation maintainers? I
volunteer for the Dutch version 
Regards,
Erik.
John W. Long wrote:
John L.
http://wiseheartdesign.com
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
–
Erik van Oosten
http://2008.rubyenrails.nl/
The jargon branch now supports language files loaded from the gem or
vendor/radiant, extensions, and the local Radiant project. Many thanks
to Chris W. for accepting my patch to Gibberish!
http://dev.radiantcms.org/radiant/changeset/470
http://dev.radiantcms.org/radiant/changeset/471
To add a language file to your extension, just add a lang/ directory and
put the appropriate YAML language files in that directory.
Sean
Erik van Oosten wrote:
I’ve attached a Dutch translation (nl.yaml) as well.
Committed:
http://dev.radiantcms.org/radiant/changeset/472
–
John L.
http://wiseheartdesign.com
I would love to translate into spanish, but need to get a working
copy (or rather, I want to upgrade to this branch.
I used: rake radiant:freeze:edge BRANCH=jargon
But am running off of gems.
It installed in /vendor/radiant/ and after starting and stopping the
server, I can seem to see a difference.
Surely I need to migrate stuff over. What needs to happen from
here. I know for extensions it is rake db:migrate:extensions, but
that is obviously wrong, and so is rake db:migrate:extensions. Any
feedback would be welcome. Then I can start translations (unless it
is already done).
-Mark
Perfect Erik
Nu hoef ik dat niet meer te doen
Translated… thanks for saving me some work
Of course if any help is needed on the dutch version just shout.
Peter.
On 7/24/07, Erik van Oosten [email protected] wrote:
John W. Long wrote:
John L.
http://2008.rubyenrails.nl/
http://www.day-to-day-stuff.blogspot.com/
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
–
met vriendelijke groet,
Peter B.
Oliver B. wrote:
John W. Long wrote:
Attach it to a ticket on the Trac site.
German translation attached to ticket. I didn’t test it though, but it’s
valid YAML and "should work"™.
Thank you. Committed:
http://dev.radiantcms.org/radiant/changeset/476
–
John L.
http://wiseheartdesign.com
John W. Long wrote:
Attach it to a ticket on the Trac site.
German translation attached to ticket. I didn’t test it though, but it’s
valid YAML and "should work"™.
Oliver