-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
welcome it, if you _could_ send changes to the fink-i18n list _prior_
We need to set this up so that the people who are working on fink itself
are given motivation to document things they are doing. If adding to
the docu
This can be done in the "delayed activation" option--English changes
get committed but not activated immediately, and the translators are
able to check them out, go over them, and can _quickly_ go over any
issues.
For a brand new document, I don't see the need to make it go live
immediately, a
> welcome it, if you _could_ send changes to the fink-i18n list _prior_
We need to set this up so that the people who are working on fink itself
are given motivation to document things they are doing. If adding to
the documentation is going to mean having a discussion about it on the
fink-i18n li
Absolutely.
In this case, since the version of the document that I put up isn't
vastly different than the last draft, I figured everybody had seen the
text.
On Mar 13, 2004, at 11:01 AM, D. Höhn wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
| Hi Alexander.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
| Hi Alexander. This looks great.
|
And just on a side not, Alexander, baba, I and all the Translators would
welcome it, if you _could_ send changes to the fink-i18n list _prior_ to
commiting them. Sometimes I am sure th
On Mar 13, 2004, at 10:49 AM, David R. Morrison wrote:
Hi Alexander. This looks great.
One thing the document is not too clear about is the message that is to
be sent to the i18n list when a change is made to the docs (by me, for
example). Are you going to handle sending those messages? Or can
Hi Alexander. This looks great.
One thing the document is not too clear about is the message that is to
be sent to the i18n list when a change is made to the docs (by me, for
example). Are you going to handle sending those messages? Or can we
perhaps modify the cvs commit mail script so that ch
