On Fri, Mar 7, 2008 at 5:45 PM, Eike Rathke <[EMAIL PROTECTED]> wrote:
> Hi Pavel,
>
>
>  On Friday, 2008-03-07 09:30:31 +0100, Pavel Janík wrote:
>
>  > Unfortunately the amount of traffic caused by Sun's particular instance of
>  > pootle translation method of OpenOffice.org translation takes a lot of
>  > traffic here. Thus I'd like to propose the setup of special [EMAIL 
> PROTECTED]
>  > mailing list
>
>  +1
>
>  I keep hitting Ctrl-R (mark the current thread as read) on this list now
>  on every subject that looks like pootle and chances that I'll miss
>  something important that way are much higher. By chance I did not miss
>  this thread though ;-)
>
>   Eike
>

To be clear, people can have problems with tool (in this case Pootle,
OmegaT) or with translatable content. About content, about terms,
about organization, this here is the right place.
Some of us use for translation Emacs, some KBabel, some poEdit, I
switched month ago from KBabel to LoKalize for example and have/had my
own problems ;) I never had a crazy idea to start whining just here
that KBabel double-click behaviour is terrific and mouse scrolling
does not scroll to next message in LoKalize, or catalogmanager
svn-support is fixed in 3.5.7 by my team-mate. :P
Right is to keep tool problems in particular tool communication
channels to avoid that some information that may be useful for
developers, get lost. There is a Pootle/toolkit developers list
([EMAIL PROTECTED]) and sure there is a list out there for
infrastructure server problems. And not everyone needs to be
subscribed... I'm subscribed to translate-devel, because I use the
toolkit on my own and not to some infrastructure lists because irc
shouts 'hey this damn (your-service-here) is down again' work very
well.
Anyways, I'm afraid too about creating new lists without clear target.
This can lead to a nightmare when lists start multiply by itself
without human interaction (ever read 'Tin Men'?). But this not the
case.
In this case Pootle/oo.o have a clear common part of interests and
many interested users, which deserve own mailing list.

ain

Reply via email to