From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: sources of the manaul
Date: Fri, 17 Mar 2006 15:00:13 +0100 [thread overview]
Message-ID: <441AC0ED.1010807@seznam.cz> (raw)
In-Reply-To: <20060317131850.GA29071@gpm.stappers.nl>
stappers@stappers.nl wrote:
> On Thu, Mar 16, 2006 at 05:17:46PM -0500, Aditya Mahajan wrote:
>
>>On Thu, 16 Mar 2006, frantisek holop wrote:
>>
>>>i think i have read something about this issue, but i don't remember
>>>where or when :)
>>
>>You can check out the manual sources from the svn respository
>>svn://ctx.pragma-ade.nl/manuals
>
>
> Is there a "read-only account" available?
> When doing a check out, how much data will be transferred?
> (So I can estimate the download time (or reconsider doing it ;- ))
>
>
>
>
>>If you prefer to browse them online they are available at
>>http://context.aanhet.net/svn/
>
>
>
> Or is that the "read-only account"?
> (Is `svn checkout http://context.aanhet.net/svn/ context-manual`
> the way to go ? )
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 can imagine advantages and disadvantages of both ways. But my very
little knowledge of SVN can not deside better solution. What is prefereble?
Vit
next prev parent reply other threads:[~2006-03-17 14:00 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 [this message]
2006-03-20 16:57 ` Vit Zyka
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=441AC0ED.1010807@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).