ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: sources of the manaul
Date: Mon, 20 Mar 2006 17:57:40 +0100	[thread overview]
Message-ID: <441EDF04.1060600@seznam.cz> (raw)
In-Reply-To: <441AC0ED.1010807@seznam.cz>

Vit Zyka wrote:
>>>You can check out the manual sources from the svn respository 
>>>svn://ctx.pragma-ade.nl/manuals
 >
> That is also my question. I would like to make a copy on my comp for 
> making current version.
> 
> My goal is to start to translate the beginners manual to Czech. Can 
> somebody suggest me the better way to do that?
> 
> - Will we store all language translations in one source files (and one 
> repository)? (in blocks <paragraph-en>...</paragraph-en> 
> <paragraph-cz>...</paragraph-cz> <paragraph-??>...</paragraph-??> ...)
> 
> - Or each language mutation will be done in a unique file set?

I have managed to make a local copy of SVN yesterday (strange I was not
successfull some week ago) and the answers are obvious now from both the
en and nl files.

* Manual ma-cb-en:
- print version is OK.
- screen version errors:
   ma-cb-screen.tex, l.18: midle -> middle
   ma-cb-style.tex, l.59,60: raster -> screen;
                             backroundraster -> backgroundscreen

There was some discussion about beginners manual (hopefully ConTeXt at 
Excursion) translation into another languages in autumn. Does somebody 
make some steps towards this goal?

How stable do you (Hans, ...) think is the English version of ConTeXt in 
Excursion (ma-cb-en) now?

----------------------------------------
* Manual context error:
This is pdfeTeXk, Version 3.141592-1.30.3-2.2 (Web2c 7.5.5) 
(format=cont-en 2006.3.18)  20 MAR 2006 15:40
entering extended mode
  %&-line parsing enabled.
  (c:/TeXLive/texmf-experim/web2c/natural.tcx)
**&cont-en cont-en.tex
(./cont-en.tex

ConTeXt  ver: 2006.02.15 17:41  fmt: 2006.3.18  int: english  mes: english
.............
(./co-en-01.tex [7.1.7]
layout          : subpage set 1 processed (size 7)
[8.2.1] [MP cont-en-mpgraph.2] [9.3.2] [10.3.3]
chapter         : - Preface
! Use of \@@opitemize1placestopper doesn't match its definition.
\doifelse #1#2->\edef \!!stringa {#1}
                                      \edef \!!stringb {#2}\ifx 
\!!stringa \!...

\setitemlevel ...temlevel \c!placestopper }\v!yes
                                                   {\def \tempsymbol 
{\getite...

\redostartitemgroup ...ommando }\setitemlevel {#1}
                                                   \ifx \listitem \empty 
\set...

\dostartitemgroup ... {\dodostartitemgroup [#2][]}
                                                   \fi
<to be read again>
                    \par
l.26
---------------------------------------------------

Vit

  reply	other threads:[~2006-03-20 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 13:18 Geert Stappers
2006-03-17 13:47 ` Hans Hagen
2006-03-20 17:58   ` John R. Culleton
2006-03-20 18:14     ` Vit Zyka
2006-03-17 14:00 ` Vit Zyka
2006-03-20 16:57   ` Vit Zyka [this message]
2006-03-17 14:19 ` Taco Hoekwater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=441EDF04.1060600@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).