Hello, I'd like to start translate cont-en.xml and keys-en.xml into russian. I looked at other translations and in the mailing list archives but it still unclear for me what to translate in these files? I have a several questions (if it's isn't annoying :) 1. Is there a common rule of what tags to translate? 2. What the meaning of cont-xx.xml and keys-xx.xml? 3. Some terms are unclear. How can I know the meaning of them (e.g. "quote" and "quotation", "intermezzo", "hfactor") in ConTeXt context :) ? 4. "setupbodyfont" -- spaces in translation must be omitted also? 5. How can I test my translation in my environment first? Thats all. Excuse me for that storm of questions :) Cheers, Arkady
Ark Shraer wrote:
Hello,
I'd like to start translate cont-en.xml and keys-en.xml into russian. I looked at other translations and in the mailing list archives but it still unclear for me what to translate in these files?
nothing if you want an russian user interface, they you need to extend the tables in mult-con.tex and mult-com.tex but since you want messages only you need to make message tables:
grep "startmessages.*english" *.tex
colo-ini.tex:\startmessages english library: colors core-buf.tex:\startmessages english library: textblocks core-dat.tex:\startmessages english library: databases core-fig.tex:\startmessages english library: figures core-fil.tex:\startmessages english library: files core-int.tex:\startmessages english library: interactions core-int.tex:\startmessages english library: versions core-itm.tex:\startmessages english library: layouts core-mis.tex:% \startmessages english library: systems core-mis.tex:\startmessages english library: systems core-obj.tex:\startmessages english library: references core-ref.tex:\startmessages english library: references core-sec.tex:\startmessages english library: structures core-ver.tex:\startmessages english library: verbatims docs-bri.tex:\startmessages english library: documents docs-she.tex:\startmessages english library: documents enco-ini.tex:\startmessages english library: encodings filt-ini.tex:\startmessages english library: filters font-ini.tex:\startmessages english library: fonts font-uni.tex:\startmessages english library: fonts hand-ini.tex:\startmessages english library: handlings java-ini.tex:\startmessages english library: javascript keep-02a.tex:\startmessages english library: addresses lang-ini.tex:\startmessages english library: linguals m-units.tex:\startmessages english library: units meta-ini.tex:\startmessages english library: metapost mult-ini.tex:%D \startmessages english library: alfa mult-ini.tex:%D \startmessages english library: alfa mult-sys.tex:\startmessages english library: check page-bck.tex:\startmessages english library: layouts page-flt.tex:\startmessages english library: floatblocks page-ini.tex:\startmessages english library: systems page-ini.tex:\startmessages english library: layouts page-ini.tex:\startmessages english library: columns page-log.tex:\startmessages english library: layouts plus-fig.tex:\startmessages english library: floatblocks prag-gen.tex:\startmessages english library: systems spec-ini.tex:\startmessages english library: specials spec-ini.tex:\startmessages english library: interactions symb-ini.tex:\startmessages english library: symbols x-set-11.tex:\startmessages english library: setup > I have a several questions (if it's isn't annoying :) > 1. Is there a common rule of what tags to translate? > 2. What the meaning of cont-xx.xml and keys-xx.xml? > these define the user interface; the english one is used to generate the other interface xml files using the data in teh mult-* files > 3. Some terms are unclear. How can I know the meaning of them (e.g. > "quote" and "quotation", "intermezzo", "hfactor") in ConTeXt context > :) ? > ah, so you want a russian interface too? nice. mult-* files are the place to look; best work with copies of those files > 4. "setupbodyfont" -- spaces in translation must be omitted also? > in the commands indeed; btw, maybe it's best to wait with translating the user intercace (commands) till we have th utf enabled pdftex (later this year) so that we can use cyrillic in commands
messages already accept utf8
5. How can I test my translation in my environment first?
compare texexec --make --all --fast en with texexec --make --all --fast --int=de en at the screen you can see that the messages get translated (i just saw that for french some translations are missing, i.e. the title: ones) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi, while we're at it: am I right, that the cont-xx.xml files are translated from the cont-en.xml with using the keys-xx.xml files? If yes (I haven't looked into it for a looong time), which strategy would be good for texshow(-web) to offer the other interfaces: a) use the other cont-xx.xml files b) translate the cont-xx.xml inside texshow(-web) using the keys-xx.xml files? Patrick -- ConTeXt wiki and more: http://contextgarden.net
Patrick Gundlach wrote:
Hi,
while we're at it: am I right, that the cont-xx.xml files are translated from the cont-en.xml with using the keys-xx.xml files?
If yes (I haven't looked into it for a looong time), which strategy would be good for texshow(-web) to offer the other interfaces:
a) use the other cont-xx.xml files
this looks ok to me
b) translate the cont-xx.xml inside texshow(-web) using the keys-xx.xml files?
not needed, ctxtools does the translation and this way we keep the conversion located at one poit what we need to figure out is a way to 'merge' patches back into the main cont-en; of course this is scriptable. I assume that you keep the relation between commands and additional edits in a separate file/database (again something we need to describe. one thing i need to do is to make reusable templates, so that we only need to edit e.g. style, color etc stuff once Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi all, texshow-web is multi-interface (again)! Next steps are * inclusion of other 'interfaces' such as api, modules, ...? * adding/editing commands * ? Which URLs did you use for downloading the examples, Taco? I remember that it was an xml file, right? Currently I store the descriptions/comments/examples in one textfield with wiki-markup. I might add a wiki-markup -> text converter. Patrick -- ConTeXt wiki and more: http://contextgarden.net
Patrick Gundlach wrote:
Hi all,
texshow-web is multi-interface (again)!
Next steps are
* inclusion of other 'interfaces' such as api, modules, ...? * adding/editing commands * ?
Which URLs did you use for downloading the examples, Taco? I remember that it was an xml file, right? Currently I store the descriptions/comments/examples in one textfield with wiki-markup. I might add a wiki-markup -> text converter.
Yes, it was an xml file (I even have some examples here), but I do not really remember where I got it from, and the current texshow does not use that stuff. The best way to fix the offline texshow IMO would be to write it anew, in ruby, and make it use an offline (perhaps flat text or xml) representation of your database that it converts to html pages for a local browser (using some variant of http://localhost:xx/). That way some of your code can be reused, and the database dump could perhaps even be sync-ed online, if the local user has a net connection. Taco
Patrick Gundlach wrote:
Hi all,
texshow-web is multi-interface (again)!
ah, great! and the help and special links work ok now too! impressive Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 7/20/06, Ark Shraer wrote:
Hello,
I'd like to start translate cont-en.xml and keys-en.xml into russian. I looked at other translations and in the mailing list archives but it still unclear for me what to translate in these files?
3. Some terms are unclear. How can I know the meaning of them (e.g. "quote" and "quotation", "intermezzo", "hfactor") in ConTeXt context :) ?
They could/should be documented on texshow.contextgarden.net (by users). \quotation{Some sentence} should give double quote around the sentence (try it). \quote{Some subsentence} should give you single quote around the sentence (both are language-dependent). intermezzo: similar appearance to figures, tables, ... Something that is placed in a similar manner as figure somewhere in text. But I never use them. hfactor stands for "horizontal (scaling) factor" I guess. There are several possibilities: - take a look at texshow.contextgarden.net - search with google or within cont-eni.pdf - try it according to the description in texshow/cont-eni
4. "setupbodyfont" -- spaces in translation must be omitted also?
Yes. Commands may not include any spaces.
5. How can I test my translation in my environment first?
As Hans said: you should probably wait half a year until Unicode is supported by pdfTeX. Ask then again. I guess that for Unicode support Hans will have to modify quite some things anyway. Mojca
participants (5)
-
Ark Shraer -
Hans Hagen -
Mojca Miklavec -
Patrick Gundlach -
Taco Hoekwater