>>>>> "Nicolas" =3D=3D Nicolas Chauveau <nicolas.chauveau@...> wr=
Nicolas> Your proposal to create a directory for each language
Nicolas> seems ok to me.
Ok, but at what level should be rooted? See below...
Nicolas> Is there a way to include the localised .py files in
Nicolas> this structure or should they stay in the main docutils
Nicolas> source directory ?
Uhm, no, I do not this would be good, even if I recognize the need to
keep some of the docs in sync with the actual doc.
Nicolas> It would be nice to define a summary of all the docutils
Nicolas> documents/guides/notes ordered by translation priority.
Yes, this would be nice, there are quite a few of them!-)
Nicolas> exemple : Do we need to translate the technicals guides
Nicolas> or should we consider that programmers are at least able
Nicolas> to read tech docs in english ? After all they have to
Nicolas> write code with comments and class names in english to be
Nicolas> consistent with existing code.
This is my opinion too. The most important are those explaining how to
/write/ in ReST (ie, spec/rst/*.txt and docs/rst/*), while those focusing=
/extending/ the framework can be postponed (spec/*.txt and
I'd like to hear some opinion on how should we proceed: is it better
to create a hierarchy spec/rst/it/ spec/rst/de/ and another under
docs/rst/, or wouldn't it be better to assume that the docs/ directory
is the preferred place for *user* documentation, and keep in a single
folder (per language, I mean!) the localized manuals? I personally
prefer the latter...
nickname: Lele Gaifax | Quando vivr=F2 di quello che ho pensato ieri
real: Emanuele Gaifas | comincer=F2 ad aver paura di chi mi copia.
email: lele@... | -- Fortunato Depero, 1929.