On Thu, Jun 30, 2011 at 1:49 AM, Hitoshi Harada wrote:
> 2011/6/30 Itagaki Takahiro :
>> On Thu, Jun 30, 2011 at 09:42, Tatsuo Ishii wrote:
>>> BTW I will talk to some Japanese speaking developers about my idea if
>>> community agree to add Japanese README to the source tree so that I am
>>> not
On tor, 2011-06-30 at 09:42 +0900, Tatsuo Ishii wrote:
> Why don't you worry about message translations then? Translation is a
> human process and there's no way to guaranteer the translation is
> perfect.
At least for message translations we have a process and sophisticated
tools that ensure that
On ons, 2011-06-29 at 18:48 -0500, Kevin Grittner wrote:
> I think this needs a well-defined and sustainable *process*, not
> just a set of volunteers. I'm skeptical that a workable process can
> be devised, but I'm willing to be proven wrong.
We had translated FAQs, each with a maintainer, which
2011/6/30 Itagaki Takahiro :
> On Thu, Jun 30, 2011 at 09:42, Tatsuo Ishii wrote:
>> BTW I will talk to some Japanese speaking developers about my idea if
>> community agree to add Japanese README to the source tree so that I am
>> not the only one who are contributing this project
>>
>>> Now, if
On Thu, Jun 30, 2011 at 10:43 AM, Tatsuo Ishii wrote:
> > IMHO, the Wiki approach seems to be reasonable than a README file.
> > It will be suitable for adding non-Japanese translations and
> > non-core developer can join to translate or fix the docs.
>
> I doubt other than developers can transla
> IMHO, the Wiki approach seems to be reasonable than a README file.
> It will be suitable for adding non-Japanese translations and
> non-core developer can join to translate or fix the docs.
I doubt other than developers can translate those README files since
the words used in the files chosen to
On Thu, Jun 30, 2011 at 09:42, Tatsuo Ishii wrote:
> BTW I will talk to some Japanese speaking developers about my idea if
> community agree to add Japanese README to the source tree so that I am
> not the only one who are contributing this project
>
>> Now, if someone wanted to set up a web site
>> My idea is defining "maintainer" for each README. Of course I am
>> ready for Japanese one.
>
> That would only cover part of the problem, and not on a permanent
> basis.
>
> How do you notice that a README has changed?
Commit messages, obviously.
> How does the community know when the cha
> I think this is basically a bad idea, because 90% of the developers will
> be unable to update such a file when changing the source code, or even
> verify whether it's an accurate translation. Thus it will inevitably
> become out-of-date, and that seems worse than useless. I'm fairly
> dubious
Tatsuo Ishii wrote:
>> The obvious concern would be "drift". As README files are
>> patched, someone would need to stay on top of the translation
>> process. Any ideas on how that could be reasonably managed?
>
> My idea is defining "maintainer" for each README. Of course I am
> ready for Japa
Excerpts from Tom Lane's message of mié jun 29 19:24:07 -0400 2011:
> Tatsuo Ishii writes:
> > I would like to propose to add Japanese translated version of README
> > in the source tree(for example against backend/storage/buffer/README).
>
> I think this is basically a bad idea, because 90% of t
>> I would like to propose to add Japanese translated version of
>> README in the source tree
>
>> Comments?
>
> The obvious concern would be "drift". As README files are patched,
> someone would need to stay on top of the translation process. Any
> ideas on how that could be reasonably manag
Tatsuo Ishii writes:
> I would like to propose to add Japanese translated version of README
> in the source tree(for example against backend/storage/buffer/README).
I think this is basically a bad idea, because 90% of the developers will
be unable to update such a file when changing the source co
Tatsuo Ishii wrote:
> I would like to propose to add Japanese translated version of
> README in the source tree
> Comments?
The obvious concern would be "drift". As README files are patched,
someone would need to stay on top of the translation process. Any
ideas on how that could be reason
14 matches
Mail list logo
