Jeroen Ruigrok van der Werven wrote:
> On 5/19/06, ymasuda <[EMAIL PROTECTED]> wrote:
> > Although there are no explicit rules for translated doc, I think there
> > should be some guidelines: for example, reStructuredText, with ".txt"
> > extension, UTF-8 for non-ASCII charsets, etc. If there are
On 5/19/06, ymasuda <[EMAIL PROTECTED]> wrote:
> Although there are no explicit rules for translated doc, I think there
> should be some guidelines: for example, reStructuredText, with ".txt"
> extension, UTF-8 for non-ASCII charsets, etc. If there are any
> additional requirements, please point th
On Thu, 2006-05-18 at 18:41 -0700, ymasuda wrote:
> I have finished Japanese (ja-jp) translations for revision 2933, and
> I wish to contribute them (after proofread patches for tutorials).
>
> Although there are no explicit rules for translated doc, I think there
> should be some guidelines: for
I have finished Japanese (ja-jp) translations for revision 2933, and
I wish to contribute them (after proofread patches for tutorials).
Although there are no explicit rules for translated doc, I think there
should be some guidelines: for example, reStructuredText, with ".txt"
extension, UTF-8 for
x27;s possible to get a '/docs/pt-br' area for my translated docs at
> the svn?
>
> I think at this moment that this documents are changed a lot of times
> in a short period, so... There is some way to sync these modifications
> to make more easy to the document translation
?
I think at this moment that this documents are changed a lot of times
in a short period, so... There is some way to sync these modifications
to make more easy to the document translations mantainer (me on pt-br
;-)) do their work?
If possible, please contact me and I'll start the job to ge
