On Sat, Jan 08, 2000 at 02:53:47PM -0500, James A. Treacy wrote:
> The real problem here is CVS. It isn't very flexible about granting separate
> permissions for different parts of the same repository. I'd love to be able
> make it so translations could only modify their portion of the repository
>
On Sat, Jan 08, 2000 at 10:14:29PM +0300, Michael Sobolev wrote:
> On Sat, Jan 08, 2000 at 02:06:14PM -0500, James A. Treacy wrote:
> > > What is the objection to many accounts per translation team?
> > Simply that we don't want to spend our time doing admin work.
> I see.
>
> > With 2-3 accou
On Sat, Jan 08, 2000 at 02:06:14PM -0500, James A. Treacy wrote:
> > What is the objection to many accounts per translation team?
> Simply that we don't want to spend our time doing admin work.
I see.
> With 2-3 accounts per translation we should be able to keep the translations
> on a good fo
On Sat, Jan 08, 2000 at 09:19:43PM +0300, Michael Sobolev wrote:
>
> To my mind, it's team coordinator who should ask for a new account in main cvs
> server, request for an account to be removed/disabled/maintained, and trace
> how
> the team members work on the translation.
>
The team coordinat
On Sun, Jan 02, 2000 at 10:57:02PM -0800, Darren O. Benham wrote:
> What is the objection to one account per translation team?
It makes difficult to trace the changes. Using only one account per team makes
the team coordinator to create her own cvs server where all changes would be
traced. This s
"James A. Treacy" <[EMAIL PROTECTED]> writes:
> > > > Also, "character entity references" can handle multibyte-characters
> > > > with ISO10646 code set.
> > > >
> > > > Japanese (Chinese characters) -> 日本語
> > > > Chinese (Chinese characters) -> 中文
> > -snip-
> > > One thing that confuses m
6 matches
Mail list logo
