Hi Roman, > > I just have to say, that I've used all your stuff (merge.xsl, convert.xsl, > simple_dict.xml) and now I'm using convert.xsl in my *.cmd when I update a > dictionary.
Ok, I will keep them. Maybe will move to a better place than, say somewhere to /tools or so... Could you describe the workflow process you are using for i18n stuff? It'll be useful for others and maybe I'll add it to docs. -- Konstantin > > Thank you. > Roman > > Konstantin Piroumian wrote: > > > From: "Horst Rutter" <[EMAIL PROTECTED]> > > > > > Sorry for not mentioning.. > > > Yes, this is portuguese, but I don't want to mislead anybody, because I am > > not. > > > The translation was provided by my wife who speaks native Portuguese. > > > > Fine! The only question I ask is: would you support your translation in > > future? Sometimes I need minor changes and cannot get a person for > > translating the needed text (e.g. Polish translation is left unsupported > > now). > > > > > > > > Send me your (latest) version of simple_dict.xml unless it's in cvs and I > > fill in the blanks. > > > > Hope to commit all the stuff today and will let you know when it's ready. > > You'll need to update only the messages_pt.xml. > > > > > > > > As far as providing simple_dict_pt.xml.. > > > The reason I did this is I thought you are supposed to: > > > Maintain a master dictionary that keeps growing (simple_dict.xml in this > > case) > > > and then whenever you add a new locale or make corrections, > > > extract out simple_dict_xx.xml using merge.xsl. (the "template") > > > Make the changes and merge back into the big one. > > > Then use convert.xsl to generate the resource bundle messages_xx.xml used > > by Cocoon. > > > This is what I concluded based on whatever documentation there was. > > > ;( > > > > That could be reasonable to keep translations in sync, but I've never used > > it that way. > > > > > > So how is this supposed to work now? > > > > Now, as only messages_xx.xml are used, I've created a stylesheet that > > transforms the source file, say simple.xml, into messages_xx.xml converting > > all the <i18n:text> and <i18n:param> tags into <message key="..." />. > > > > > you edit simple_dict.xml and then use convert.xsl to regenerate the > > message catalog for the locale in question? > > > That's it? > > > > No, I don't touch the simple_dict.xml anymore. Moreover, I was going to > > remove all the legacy stuff (merge.xsl, convert.xsl, simple_dict.xml) from > > CVS, but it seems that I have to rethink it. > > > > Never thought that somebody went so far as using those stylesheets ;) > > > > Konstantin > > > > > > > > Horst > > > > > > ----- Original Message ----- > > > From: "Konstantin Piroumian" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Tuesday, April 23, 2002 4:50 AM > > > Subject: Re: special characters for i18n > > > > > > > > > > > > > > Hi! > > > > > > > > Thanks for sending this. I guess that this is Portuguese? > > > > Could you also translate this line: "Portuguese translation was made by > > > > <your-name /> [<your-email />]" and the country name of Portugal? > > > > > > > > Btw, the simple_dict_pt.xml is in the old dictionary format and it's not > > > > supported any more. Why do you use it? > > > > > > > > -- > > > > Konstantin Piroumian > > > > [EMAIL PROTECTED] > > > > > > > > > Thanks, > > > > > All very useful information. > > > > > Still the solution to my problem was that I (blind me!) did not > > realize > > > > > that the stupid MS WordPad writes UTF-16. > > > > > Now I am aware of saving my files in UTF-8 (with MS Notepad) and voila > > > > > here goes another extension for the i18n sample. > > > > > (gotta move over to Debian one of these days..) > > > > > > > > > > For anyone of the commiters who cares I have attached > > simple_dict_pt.xml > > > > > and messages_pt.xml > > > > > (Was not sure if I should direct this directly to Konstantin > > Piroumian) > > > > > > > > > > Horst > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > Please check that your question has not already been answered in the > > > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > > > > > > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > > > > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > Please check that your question has not already been answered in the > > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > > > > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > > > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > > > > > --------------------------------------------------------------------- > > Please check that your question has not already been answered in the > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>