Hello,
Could you please give us an update of the progress in the integration of the i18n internationalization branch. I have seen in the roadmap that the version 1.5 is due in less than a month. Is that an approximate date or should we expect the new version by that time?
Plese not that it is not my intention to put any kind of pressure on you. It is only to plan ourselves.
Thanks,
Daniel
It is progressing and we anticipate that it will be available in 1.5. The listed date for the release of 1.5 is not set in stone, but it is safe to anticipate it being released before the end of the year.
Great!
I can help with catalan and spanish.
Waiting for 1.5!
Please contact me if you need support for the German translation.
I'm looking forward to the localization features in 1.5!
I (and others earlier in the thread) are also willing to help with a German localization.
Is the Omeka team planning to release v1.5 in multiple languages or just have it be "localization ready"?
These organizational issues are up in the air a little, since what works best might not be immediately clear and how things get packaged up will depend on how many languages actually have work done on them.
Right now, the plan is to have a string freeze pretty soon, so we can have enough time for at least some languages to have translations actually included with the 1.5 release.
This being our first go-round of a release with translation support, we're going to be playing it by ear a little with the timeline, I think.
Good news! We're ready to open up the doors to translations. We're using the Transifex service, so you'll need a free account there. Read more about it in our documentation.
Happy translating, and many thanks!
Thank you! Is there a way to test the translations?!
Is it ok to test with the https://omeka.org/svn/branches/i18n/ ?
Shoul I just put the pot file there?!
The current code is available at https://github.com/omeka/Omeka, we're not using our old SVN (or that i18n branch) anymore.
The correct version that supports translations is called 1.5-dev, and is the "master" branch on GitHub.
You can use the Omeka GitHub repository similarly to SVN (only using Git, of course), or you can also get GitHub to generate a zip for you to download by clicking the "ZIP" button.
In any case, to test a translation on 1.5-dev, you place the .mo file in the application/languages folder, then set the "locale" setting in config.ini to the part before ".mo."
Apologies if this all sounds a little confusing at this stage. We'll also make an easier-to-use pre-release zipped copy of 1.5 for people to test with, so you might want to wait for that option instead. For this zipped version, we'll include all the necessary files for any translations that have been submitted on Transifex, and all you'll have to do is set the "locale" setting for your desired language.
All good here! I'm building a small demo collection to present to my fellow colleagues. It should be added that 1.5-dev is not working fully OTB. It needs fiddling, but it is OK in the end! Thanks for this.
OK, I have succeeded in building this 1.5-dev portable Omeka on top of an XAMPP app. The language specified is Romanian, but if you need to test another lang pack you may simply put the files in the languages folder and make the appropriate modification in your config.ini.
Remember before stating XAMPP to regenerate the app's settings launching xampp setup before the controller.
Have fun!
Dear friends,
Translating the strings for Simple Pages I came across with this little thing:
In the
Occurrences: models/SimplePagesPage.php:90
String ID: The slug for your page must not be a forward slash.
it is specified that the slug is not to contain a forward slash and further down below
Occurrences: views/admin/index/form.php:22
String ID: The URL slug for the page. Automatically created from the title if not entered. Allowed characters: alphanumeric, underscores, dashes, and forward slashes.
it is legal to have it. Hmmmm... a bit puzzled here. it means you may have something like [URL]/slug/moreslug ?
Thanks
Obviously, there's a little confusion in those messages, and I think it boils down to the first string being confusing.
A SimplePages slug can contain a forward slash, so you can simulate a directory structure with your pages. What you can't do is make a slug that's only a forward slash and nothing else (just /).
right! thnak you for clearing this up! Cheers
You must log in to post.
Omeka is a project of the Roy Rosenzweig Center for History and New Media, George Mason University. Omeka and the Omeka logo are registered trademarks. Copyright © 2007–2012 CHNM.