Hi I'm using Koha2.2.2b, in the parameters module suddendly i saw one msg in MARC check ...it shows a mistake that can BREAK Koha's database! when i clicked : item fields: ALL items fields MUST : # be mapped to the same tag, # and they must all be in the 10 (items) tab i somehow tried to modify the tag structure .. but tat error was not going...Someone suggest me a idea so tat it would be a great help to u... Suffering with this problem...(coz it may affect the database...) Priya.. ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi! Sorry if my question is answered somewhere else. I couldn't find it by myself until now. Thanks for pointing me any resource. Being a newcomer to Koha, I'm seeing many translation/localization requests in this list (specially spanish, in which I'm interested too). So, among all the spanish Koha users we could maybe have enough taskforce to maintain an spanish version updated. As far as I've read in the code, Koha's localisation is based on copy-paste of HTML templates and translation of strings contained in them. What to do with Koha updates is not clear, but it seems that the solution would be performing some diffs between files and editing the old localized code so that it looks like the new english one. When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions. (I'm doing some assumptions... thanks for correcting me) So, is there any roadmap for a new I18N/L10N schema that would simplify the Localisation system, so that english becomes Just Another Language? gettext/po files-like systems is the most used solution, but I don't know what's the idea of the benevolent dictators of this great software. ;-) BTW, I could help in the I18N process. Thanks in advance. -- Garikoitz Araolaza CodeSyntax garaolaza at codesyntax.com Azitaingo Industrialdea 3 K E-20600-EIBAR Tel: +34 943 82 17 80 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Garikoitz, Welcome to Koha! In fact, we have a system of .po files for translation. There are general instructions here: http://lists.katipo.co.nz/public/koha/2004/004061.html Hope that helps. With Koha 2.4 we'll make sure that all the major language communities using Koha are represented before we do a release -- and that we have official docs on how to translate. If you'd like to be involved in the translation process that would be great! We have an IRC meeting on Thursday: irc.katipo.co.nz:6667 #koha To see what time it will be in your area check out ... http://makeashorterlink.com/?S5072361B Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf@liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Who's preparing the agenda for Thursday and can i18n be on it, please? I'd also love news on koha world and the other web sites. -- MJR/slef http://www.ttllp.co.uk/koha/ _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Garikoitz Araolaza wrote:
Being a newcomer to Koha, I'm seeing many translation/localization requests in this list (specially spanish, in which I'm interested too). So, among all the spanish Koha users we could maybe have enough taskforce to maintain an spanish version updated.
That's will be great. There is a translation, that I've found credited to me. I haven't done anything, I Think that it was something done here (ORT Uruguay) by Ernesto Silva, or by someone in Argentina. If someone can work in the .po files we could have a nice translation. It would be intersting to enhace the templates.
As far as I've read in the code, Koha's localisation is based on copy-paste of HTML templates and translation of strings contained in them. What to do with Koha updates is not clear, but it seems that the solution would be performing some diffs between files and editing the old localized code so that it looks like the new english one.
You're right, there's also some messages in the database.
When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions.
Never tried this. Solving this will require some changes.
So, is there any roadmap for a new I18N/L10N schema that would simplify the Localisation system, so that english becomes Just Another Language? gettext/po files-like systems is the most used solution, but I don't know what's the idea of the benevolent dictators of this great software. ;-) BTW, I could help in the I18N process.
As far as I know there no such process, some is needed to take care of it. Some latin americans have done some work, but not in an organized maner. Maybe you can organize this. Andres _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions.
Never tried this. Solving this will require some changes.
In the OPAC we had (have?) a "change language" option, which just changed templates - rather than a whole nother copy of Koha. I think that no one has done it on the intranet because they haven't needed to rather than because they can't? Cheers Rachel -- ----------------------------- Rachel Hamilton-Williams General Manager Katipo Communications Ltd Phone: +64-4-934 1285 Mobile: 021 389 128 E-mail: rachel@katipo.co.nz Web: www.katipo.co.nz _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
You're right !!!!!, Since we did a complete "face lift" in both the OPAC and the Intranet we took away that posibility. I've almost forgot about it. Andres Rachel Hamilton-Williams wrote:
When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions.
Never tried this. Solving this will require some changes.
In the OPAC we had (have?) a "change language" option, which just changed templates - rather than a whole nother copy of Koha. I think that no one has done it on the intranet because they haven't needed to rather than because they can't?
Cheers Rachel
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
You're right !!!!!, Since we did a complete "face lift" in both the OPAC and the Intranet we took away that posibility. I've almost forgot about it. Andres Rachel Hamilton-Williams wrote:
When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions.
Never tried this. Solving this will require some changes.
In the OPAC we had (have?) a "change language" option, which just changed templates - rather than a whole nother copy of Koha. I think that no one has done it on the intranet because they haven't needed to rather than because they can't?
Cheers Rachel
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Garikoitz Araolaza wrote:
Being a newcomer to Koha, I'm seeing many translation/localization requests in this list (specially spanish, in which I'm interested too). So, among all the spanish Koha users we could maybe have enough taskforce to maintain an spanish version updated.
That's will be great. There is a translation, that I've found credited to me. I haven't done anything, I Think that it was something done here (ORT Uruguay) by Ernesto Silva, or by someone in Argentina. If someone can work in the .po files we could have a nice translation. It would be intersting to enhace the templates.
As far as I've read in the code, Koha's localisation is based on copy-paste of HTML templates and translation of strings contained in them. What to do with Koha updates is not clear, but it seems that the solution would be performing some diffs between files and editing the old localized code so that it looks like the new english one.
You're right, there's also some messages in the database.
When trying to run Koha in a bilingual environment, I understand that two instances of Koha should be run, and give access from different URLs to the different versions.
Never tried this. Solving this will require some changes.
So, is there any roadmap for a new I18N/L10N schema that would simplify the Localisation system, so that english becomes Just Another Language? gettext/po files-like systems is the most used solution, but I don't know what's the idea of the benevolent dictators of this great software. ;-) BTW, I could help in the I18N process.
As far as I know there no such process, some is needed to take care of it. Some latin americans have done some work, but not in an organized maner. Maybe you can organize this. Andres _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
participants (6)
-
Andrés Tarallo -
Garikoitz Araolaza -
Joshua Ferraro -
MJ Ray -
priya ilango -
Rachel Hamilton-Williams