Hi, I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread So the question is: - what can go out - what should go in - what should be updated as well as: - who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters) Hans
On 11/21/05, Hans Hagen
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation)
I have no so many free time but I could organize (I hope) in VnOSS community for vietnamese translation of ConTeXt's manuals. Regards, -- http://vnoss.org Vietnamese Open Source Software Community
Quoting "Hans Hagen" :
-- was pragma@wxs.nl on Nov 21, 2005 at 11:03:49 --
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
I'll be glad to help for the french translation. By the way, what about the translation of the context core? Olivier
A las 23:03 del lun 21 nov, Hans Hagen tuvo a bien escribir:
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
I'd like to contribute with the spanish translation -- José Antonio Rodríguez jar@eideia.net ------------------------ 'El Fuego vive en los corazones de quienes aman el futuro' (Agni Yoga)
I could think of translating to swedish. Depends on how much work it
is and about if it must be done before that or that day. I got pretty
much to do at work...
/Micke P
On 11/21/05, Hans Hagen
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
I could help with this translation to Swedish, although I of course
also have time constraints.
Half the work and twice the fun!
Johan
2005/11/22, Mikael Persson
I could think of translating to swedish. Depends on how much work it is and about if it must be done before that or that day. I got pretty much to do at work...
/Micke P
On 11/21/05, Hans Hagen
wrote: Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
-- Johan Sandblom N8, MRC, Karolinska sjh t +46851776108 17176 Stockholm m +46735521477 Sweden "What is wanted is not the will to believe, but the will to find out, which is the exact opposite" - Bertrand Russell
Hi, Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
Here is my 2 cents (numbers refer to the sections).
- what can go out
\setupsectionblock (4) \indenting (34) twoletter language shortcuts (37)
- what should go in
\mainlanguage endnotes environments arranging&papersize quotes"ations&narrower forms overlays typescripts regimes encodings? columnsets? natural tables?
- what should be updated
special characters: explain e.g. \{ and \[ (3) rename Headers => Sectioning or Structure (5) perhaps TABLE gets to much attention (11) rename Definitions => Descriptions (15,16) comments should be explained earlier (37) modules (38) Cheers, Taco
Hi, Taco Hoekwater wrote:
special characters: explain e.g. \{ and \[ (3) That brings me to a thing I miss a lot. My LaTeX book had in the end a few pages with special characters, which is the main reason I still look in it.
I'd like to see - preferably at the last pages of the manual so one finds them quickly in the printed version: - somewhere: -, --, ---, |-| etc. - somewhere: \/ (German example: Auf\/lage) to prevent the ligature - \dots - How to enter: $ & % # { } \ (esp. the "\") - text mode accents \'o \type{\'o} (maybe mention \oaccute as well?) \SS\ \type{\SS} and text mode symbols \copyright, \S, ... - mention that for different languages some additional methods exists (e.g. de "u -> ü, "s -> ß; or for Greek; or ...) - mathematical input Math accents Greek Symbols Maybe also AMS Symbols In short I mean basically the following tables from "\LATEX Kurzbeschreibung" (http://www.ctan.org/tex-archive/info/lshort/german/l2kurz.pdf): - Page 19, Table 4 (accents and special letters) and Table 5 (symbols) - page 32ff, Table 6 (math accents), Table 7 (small Greek letters), Table 8 (capital Greek letters), Table 9 (further symbols), Table 10 ("big" operators), Table 11 (binary operators), Table 12 (relations), Table 13 (negated relations), Table 14 (arrows) and Table 15 (braces) Tobias
Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
31.2. \showbodyfont[cmr] 32.2. has to be rewritten I guess (write something about \enableregime[utf-8] and something about encodings) 38 (using modules): to be rewritten C (auxilary files): mention texutil --purge[all] What could be added: - Tables: Natural tables (already mentioned by Taco). I just realized that this is the only manual where the "usual" tables are actually explained. I was looking for the explanation in cont-eni before. - Bibliography - Slides: some basic example with \usemodule[pre-whatever] to show the user that making slides is no more difficult than making an A4 document - Metafun: some basic examples and a reference to the manual - XML: a basic example - mention XeTeX & Aleph somewhere (at least under section with fonts or lnguage-specific issues)
as well as:
- who will participate (in translation)
Slovenian translation is not rentable yet :(
- how to deal with localization (maybe dedicated language related chapters)
Not a bad idea. Encodings, regimes, \mainlanguage, using different interface, French "active characters", quotations, Greek, Vietnamese, Russian, ... under the same hood. Mojca
Le 23 nov. 05 à 21:15, Mojca Miklavec a écrit :
What could be added: - Tables: Natural tables (already mentioned by Taco). I just realized that this is the only manual where the "usual" tables are actually explained. I was looking for the explanation in cont-eni before. - Bibliography - Slides: some basic example with \usemodule[pre-whatever] to show the user that making slides is no more difficult than making an A4 document - Metafun: some basic examples and a reference to the manual - XML: a basic example
I agree with the above. And for people comming from LaTeX, it would be nice to see also : - a basic exemple for creating html from ConTeXt, - some mathematics Maurice,
Maurice Diamantini (dom) schrieb:
Le 23 nov. 05 à 21:15, Mojca Miklavec a écrit :
What could be added: - Tables: Natural tables (already mentioned by Taco). I just realized that this is the only manual where the "usual" tables are actually explained. I was looking for the explanation in cont-eni before. - Bibliography - Slides: some basic example with \usemodule[pre-whatever] to show the user that making slides is no more difficult than making an A4 document - Metafun: some basic examples and a reference to the manual - XML: a basic example
I agree with the above. And for people comming from LaTeX, it would be nice to see also : - a basic exemple for creating html from ConTeXt,
I would argument that it is easyer to create ConTeXt from a propper XML/XHTML source! But as it is the beginner manual a reference to the XML manual should be enough.
- some mathematics
not really a big problem, but you have the choice also to use MathML. Wolfgang
Le 25 nov. 05 à 10:47, Wolfgang Zillig a écrit :
Maurice Diamantini (dom) schrieb:
And for people comming from LaTeX, it would be nice to see also : - a basic exemple for creating html from ConTeXt,
I would argument that it is easyer to create ConTeXt from a propper XML/XHTML source! But as it is the beginner manual a reference to the XML manual should be enough.
- some mathematics
not really a big problem, but you have the choice also to use MathML.
This is always the same difference of opinion : - Some people like to see the only input format to be xml (write xml for math, ...) and think *TeX as one of the output formats (as for pdf, xhtml, ps...). - Other poeple (specialy those coming from TeX community) prefere writing by hand (yes it does yet exists !) some readable and lite document with math formula or other, then convert then as pdf printable output and (if possible also some (x)?html resizable ouput format But perhaps I doesn't understand ConTeXt xml features. Perhaps context is able to generate xml files instead of only reading them? If it is the case, then let me know, as it could solve the html navigator problem. So I'll have to learn more about xm and xml styles? Maurice
Hi!
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
As a beginner myself and typesetting in Portuguese I can tell you what I had troubles with: - mainlanguage - Special characters as º (\ordmasculine and stuff like that). And maybe not in the beginners manual but I think there should be an updated manual about how to install context. I'm still using a context version from 2004.08 as it is the only one it worked for me. I downloaded as far as I remember the file mswincontext.zip , the stand alone version of context, but the newer versions need Perl and Ruby to be installed. By the way... Are there any sugestions on the installation of Ruby and Perl on windows ? I think there should be some instructions on how to install mswincontex.zip on any system, because the dificulty in installing Context might drive some users away. Anyway... Context is great ! I'm now typesetting my first document with it. :) Thank you, Miguel Queirós
Miguel Queiros schrieb:
Hi!
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
As a beginner myself and typesetting in Portuguese I can tell you what I had troubles with:
- mainlanguage - Special characters as º (\ordmasculine and stuff like that).
And maybe not in the beginners manual but I think there should be an updated manual about how to install context.
I'm still using a context version from 2004.08 as it is the only one it worked for me. I downloaded as far as I remember the file mswincontext.zip , the stand alone version of context, but the newer versions need Perl and Ruby to be installed.
By the way... Are there any sugestions on the installation of Ruby and Perl on windows ?
http://www.activestate.com/ they provide avtivepearl. It's no problem to install it. http://www.ruby-lang.org/en/ there you get ruby. They provide a link to the "one click ruby installer" which you will find here: http://rubyinstaller.rubyforge.org/wiki/wiki.pl there is the after installing you should check if the *.exe of perl and ruby is in the default path. you can easily check in the command line by calling ruby --version and perl --version To get the context scripts running they should also be in the default path (this given path is valid for my miktex installation, you probably have to change it)! C:\texmf\scripts\context\perl C:\texmf\scripts\context\ruby I had to add them manually. Regards Wolfgang
http://www.activestate.com/ they provide avtivepearl. It's no problem to install it.
http://www.ruby-lang.org/en/ there you get ruby. They provide a link to the "one click ruby installer" which you will find here: http://rubyinstaller.rubyforge.org/wiki/wiki.pl there is the
I'v had downloaded already Perl from activestate, and I believe I came across the ruby installer you mentioned but didn't installed it yet...
after installing you should check if the *.exe of perl and ruby is in the default path. you can easily check in the command line by calling ruby --version and perl --version
To get the context scripts running they should also be in the default path (this given path is valid for my miktex installation, you probably have to change it)! C:\texmf\scripts\context\perl C:\texmf\scripts\context\ruby
I had to add them manually.
Thanks for you information... Pragma site also mentions ghostscript, is it realy needed or only if you want postscripts ? Once again thank you, Miguel Queirós
Hi Hans, Thank you for your great work. Regarding the beginners manual your are going to update, I have two or three suggestions. To begin with, I think we should designate a volunteer group of people on this list to do some tasks in "parallel": 1) Since the installation of ConTeXt seems to be not so easy for everyone, we should have at least three subgroups of people experimenting, and then explaining, how to install and update ConTeXt on Linux, Windows, MacOS X. Once each subgroup has carried out the experimentation of the "How to..." instructions, they would send them to you so that you can include them in the Beginners Manual (abbreviated BM in the sequel...). It is important to include in each subgroup a "wizard" and an "amateur beginner": otherwise the "How to..." instructions may result in something not really usable by real beginners. For my part I am volunteering to be a (rather dumb...) beginner regarding installation on MacOS X, and its use with XeTeX. The same observation applies for the use of ConTeXt with non roman languages under various operating systems. 2) We should divide the BM in $n$ parts ($n \geq 2$... but maybe $n=10 $) and designate one or two individuals for each part to test ALL the codes and examples you give in the BM to make sure that they work fine with a "basic" install of ConTeXt. 3) Two great features of ConTeXt are its versatility regarding Metapost and presentations. In the BM these features should be presented in a transparent way, since most beginners would not have the patience or the technical knowledge of going through the source files. Best regards: OK On 21 nov. 2005, at 23:03, Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Hi Hans, Thank you for your great work. Regarding the beginners manual your are going to update, I have two or three suggestions. To begin with, I think we should designate a volunteer group of people on this list to do some tasks in "parallel": 1) Since the installation of ConTeXt seems to be not so easy for everyone, we should have at least three subgroups of people experimenting, and then explaining, how to install and update ConTeXt on Linux, Windows, MacOS X. Once each subgroup has carried out the experimentation of the "How to..." instructions, they would send them to you so that you can include them in the Beginners Manual (abbreviated BM in the sequel...). It is important to include in each subgroup a "wizard" and an "amateur beginner": otherwise the "How to..." instructions may result in something not really usable by real beginners. For my part I am volunteering to be a (rather dumb...) beginner regarding installation on MacOS X, and its use with XeTeX. The same observation applies for the use of ConTeXt with non roman languages under various operating systems. 2) We should divide the BM in $n$ parts ($n \geq 2$... but maybe $n=10 $) and designate one or two individuals for each part to test ALL the codes and examples you give in the BM to make sure that they work fine with a "basic" install of ConTeXt. 3) Two great features of ConTeXt are its versatility regarding Metapost and presentations. In the BM these features should be presented in a transparent way, since most beginners would not have the patience or the technical knowledge of going through the source files. Best regards: OK On 21 nov. 2005, at 23:03, Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans
Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
I recommend that the original manual in English be kept in the translation. I mean that we put the translation of each paragraph just after the English version, so people can refer to the original manual easily when they don't fully understand the translation. I've seen a Chinese translation of python manual in this manner, which I think if great for me. Just like this: [......paragraph one..............English version.................] [......paragraph one..............translated version..............] [......paragraph two..............English version.................] [......paragraph two..............translated version..............] ......... ......... [......the last paragraph ..............English version.................] [......the last paragraph ..............translated version..............] Hope my bad English didn't confuse anyone. Regards, xiaojf
Hi, this is a follow-up to the first message... Are you (Hans) collecting the sugesstions from this thread or should they be wikified? Patrick -- ConTeXt wiki and more: http://contextgarden.net
Hans Hagen wrote:
Hi,
I'm going to clean up the beginners manual (at least the source code) so i think this s a good moment to pick up the 'translation' thread
So the question is:
- what can go out - what should go in - what should be updated
as well as:
- who will participate (in translation) - how to deal with localization (maybe dedicated language related chapters)
Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
I can do some work with the Chinese translation if there is no other people going to take this job. One thing I have to mention is that I'm not good at ConTeXting, and I don't have too much time either, it will probably take a little long time for me to translate the whole manual. But I can promise that I will try my best to do a good job if I take the job. Regards, xiaojf
Hans Hagen wrote:
I'm going to clean up the beginners manual
Yippee! :-) Having read one printout to shreds I really appreciate this...
- what should go in
As has been suggested here to an extent, there should be attachments (or separate smaller manuals) on how to install and update ConTeXt in different operating systems (Mac OS 10.4 was a breeze even for a new Mac user, Windows is a great pain in the butt every time; still running TeXLive 2004 ConTeXt on this machine because I can't afford to break anything). As I probably should do it for work anyway, I'm willing to write the part for MsWinConTeXt (for Win 2000/XP) as long as I get at least until the end of the year. I also suggest writing a separate set of instructions for those people who migrate from LaTeX (like my brother did) and for those who migrate from MSWord (like I did) or Apple's Pages (or similar word processing software). I strongly feel that the beginners' manual per se should be for ALL beginners and shouldn't refer to either Word or LaTeX. Again, as I probably have to write it at some point anyway, I'm willing to chip in for the MS Word part and I might even be able to write a draft for others to fill in with.
- what should be updated
Tables is what would be really useful. This far I've only used tabulate and \table, but I have a faint idea that "natural tables" would be the real solution to my problems - but finding info on them has been so challenging that I've given up this far. I also personally feel that a totally different approach to the fonts chapter would make my life a lot easier. I'm sure this partly relates to my Windows background, but for example the term "font family" was totally alien to me when I started using ConTeXt. And of course, much of the first weeks with ConTeXt (in Windows) were overshadowed by the important question of "how to make the fonts and font switches work at all". I still don't understand the system at all, so even though I've successfully gotten a few of the TeXLive fonts to work, I always have to refer to my older ConTeXt documents to copy the code that has worked at least at some stage. [In Word, you switch the font of the Normal style from Times New Roman to Century Schoolbook with about three clicks of the mouse - in ConTeXt the same may be a three-hour or three-day operation, at least with my not-even-intermediate skills... I love ConTeXt, I hate fonts.] The order of things in the beginners' manual has often frustrated me as I feel that "same stuff" is split in different places all over manual. I have not dealt with math, but when I taught word processing with Word, these would be things that come up in the very, very beginning: - how to change the font (family, size, emphasis) - how to change the paragraph (line spacing, paragraph spacing, indents, alignment) - how to print preview i.e. see the document as laid out on paper (in ConTeXt this would be "how to compile and view; maybe put more detailed instructions into the ConTeXt in Unix/Linux/Mac/Windows attachment/manual and just refer to these) - how to change the margins [I had REAL problems with this in ConTeXt, the whole context is so different; but this should probably go into the "ConTeXt for word processor users" chapter] [- how to save and retrieve a document; not really an issue with ConTeXt, I suspect all users are this much computer literate] Next step is often additional text features: - headings (in Word, "header" is only top part of page, the section/chapter titles are called headings) - lists (i.e. itemize in ConTeXt) - page numbers (many Word users never use their header/footer for anything else!) - page breaking - hyphenation And, as many people migrate to ConTeXt when having to deal with large documents and/or math, the next step for many would probably be: - figures (i.e. graphics) - tables - footnotes - header & footer - formulae, units, math otherwise - special characters! - registers, references - interactivity? If ConTeXt comes nowadays with modules, those should probably get a more prominent position in the manual and obviously a lot more detailed explanation than the current one. If I've understood the concept correctly, the modules are comparable to Word templates, but this far the information has been so split that I haven't bothered to piece it together to actually even try to use a module, not to talk about making one (although that bit probably belongs to the big manual).
- who will participate (in translation)
I can do Finnish, it shouldn't take that long once the English original is ready. A bunch of LaTeX stuff exists in Finnish and that should help with the terminology (should probably try to stick to existing stuff) and I can possibly enlist brother to review what I've done, if there're no other Finnish speakers on this list. I'll also be quite happy to proof the Swedish manual but as there are native speakers of Swedish on this list, I'd rather leave the actual translation work to them (especially when I use Swedish as spoken in Finland, which sometimes makes a difference).
- how to deal with localization (maybe dedicated language related chapters)
Yes, definitely. Having now worked with translations of originally English ConTeXt document to German and Spanish I've had to look for answers for the following problems: - hyphenation (how to turn it on and how to prevent it) - labels in captions and references (how to switch language, how to adjust) - regiments - character sets (especially non-Latin stuff) - punctuation rules (for example one vs. two spaces after period) Sometimes I'd really, really love to have a list of what characters and languages ConTeXt is/is not capable of coping with, just a quick reference would help... A few thoughts from the Windows front, Mari
participants (18)
-
Hans Hagen
-
Johan Sandblom
-
Jose Antonio Rodriguez
-
Mari Voipio
-
Maurice Diamantini
-
Maurice Diamantini (dom)
-
Miguel Queiros
-
Mikael Persson
-
Mojca Miklavec
-
Olivier
-
Otared Kavian
-
Otared KAVIAN
-
Patrick Gundlach
-
Taco Hoekwater
-
Tobias Burnus
-
VnPenguin
-
Wolfgang Zillig
-
Xiao Jianfeng