Grzegorz Adam Hankiewicz <firstname.lastname@example.org> writes:
> I don't see any exceptions in HACKING related to
> documentation. Previous posts contradict what you say
> too, unless I misunderstood both HACKING and those posts.
We can put an exception in there if you need.
The HACKING guidelines should not get in anyone's way. If you find
them so restrictive that they are a deterrent to you doing work, then
let's loosen them for translations. I'm pretty sure the other
developers would agree.
Note that message 69290 was about two things: formatting, and clarity
(mentioning the name of the removed directory). Of the two, clarity
is more important. It's not really that important that the same
format be used for code commits as for translation commits, though if
> I could discuss this if the exceptions you talk about are clearly
> defined, which currently is not the case. Have these exceptions
> been communicated to other book translators?
I've updated HACKING in r11227, please take a look and see if the new
guidelines are clearly enough defined. (I'll do a separate post to
make sure no other developers object to this change.)
> Thanks. It's just that I don't welcome extra commit messages
> unrelated to the task I'm interested in, though.
> Another icky problem would be non utf8/ascii logs/contents in commit
> emails, as sadly documented around line 440 of commit-email.pl. I
> currently fixed it hacking the charset and using an additional script
> to translate svn utf8 logs into latin1 before they are included in
> the mail.
> This raises another issue not discussed in HACKING, which is non
> English log messages and how they should be used, if at all allowed.
I'm pretty neutral in that discussion, I'll let people who have
opinions sort it out :-).
> OTOH each translator is then forced to follow (IMHO) unproductive
> rules and deal with a higher volume of emails. Since you demonstrate
> willingness to lessen the former and translators might be able
> to deal with the latter, I will discuss this on the mailing list,
> because until now I only spoke for myself.
> However, I still think that subversion code development and
> translation of documentation are tasks better dealt with separately,
> in a modular approach.
This may possibly still be true. Even though HACKING is adjusted now,
I don't mean that to force a decision on you. I just didn't want
HACKING to be in your way. You and the other translators and Erik can
work out the best procedure from here...
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Oct 4 18:12:25 2004