Hi Grzegorz,
As promised I'll try to answer your questions below. I hope the
answers are enough to your liking so that you will reconsider and want
to be part of the Subversion repository for your book development.
> On 2004-09-18, Grzegorz Adam Hankiewicz <gradha@titanium.sabren.com> wrote:
> > The methodology we are using to translate is to take
> > a snapshot of the english book and translate it,
That part is great, I think, since then there will be little doubt
which changes should have been incorporated in the book and which
don't. Also it leaves little room for doubt about what work is left to
do.
Do you (or will you) have a file in your tree somewhere which states
which rev is currently being translated?
> > which results in partially translated .xml files. However, in
> > http://svn.collab.net/repos/svn/trunk I see that other translators
> > of the book only send you the completely translated files.
Since you have a clear policy on what translation is left to be done
and from which revision, I see no problem in having partially
translated files in the trunk repository. The trunk is absolutely
where this kind of development should take place.
> > We
> > also have README like files and custom makefile to generate a
> > partially translated spanish version of the book. Can I include
> > these in future patches or you only accept the .xml files (only
> > if they are complete)?
If the translation is going to be part of the main repository (and we
want that) then you are going to need some room to do what you need to
do for your translation. So, if you are going to have README,
TRANSLATING or other administrative files, then those are part of your
translating administration. Ofcourse you will be allowed to run the
administration that goes with the work.
For the Makefile; many projects' makefiles run only on one platform
(mostly Linux) or on one 'make' variant. Subversion supports a very
wide range of platforms and 'make' variants. It would be expected that
your Makefile supports these same targets, so if you are going to add
a Makefile, we really want to encourage you to make sure it runs on
many platforms and many 'make' variants. Apart from that I don't see a
problem with you having your own Makefile.
> > Rubén just asked if you could provide a mailing list for discussion
> > of Spanish translation issues. In my previous translation projects
> > I've never needed more than a few email exchanges to solve
> > problems, but I was working mostly alone and asking doesn't hurt.
The mailing list has been setup now. I saw the first mails being exchanged.
Let me know what you think of my answers. I seriously hope you are
willing to join the main Subversion repository. If you do, please tell
me so, so that I can start the required process.
> > Should I announce the translation project on
> > announce@subversion.tigris.org? Maybe somewhere else?
That would be a good place to do so. It would be even better if you
could mention a URL for your project within the Subversion repository.
:-)
> > It would be nice if the web page at http://svnbook.red-bean.com/
> > mentioned translation projects and redirected readers to the in
> > progress documents or maybe another web page. This increases the
> > project's awareness to subversion users and increases the chance
> > of somebody joining the translation project or reading/reviewing
> > the work done so far.
As far as I have seen, you've been contacted by C Mike Pilato about
the svnbook site and related matters. (I can't tell you anything about
those, as you probably know now.)
> Regardless of hosting issues, I'd still send periodic patches to
> include in http://svn.collab.net/repos/svn/trunk once somebody
> answers the first question I quoted. And I will still push you
> towards internationalising the page at http://svnbook.red-bean.com/.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 2 20:15:18 2004