Re: [G11ntoolkit-developer] RE: Further to my feature request...

[Raymond M. <bio...@ya...>]

Hi Bill,

> I am sorry that I have taken so long to respond. I am changing my DNS routings 
> and my hosting service and I guess it is playing havoc with my mail and my ability
> to post to this list.  

No problem.

> I agree that the XLIFF Editor should be packaged separately. The editor depends 
> on classes in the G11NToolKit but the toolkit does not depend on the editor. 

Okay, good. That makes the base toolkit that much smaller. Implementers will be
more inclined to use it if it is smaller.

> What other parts of the toolkit are you thinking may need to be separated?

Not exactly sure at present. The XLIFF DB and DB update are shown as optional 
in the process diagram, are they possibilities?

> You have a concern about overlap in function between omegat and the toolkit. 
> Do you need finer granularity in the toolkit classes or are you more concerned 
> at a higher level with overall function. If you need a finer granularity we can 
> probably just factor the classes to see where we can split them. This makes 
> more classes but may make using the toolkit easier.    

Bare with me, I'm still looking at the toolkit mostly from a top level view right now.

I'll have to comment about granularity at some later time.

What I do think would be interesting is to have a general mechanism to pipeline the
overall localization/translation from end to end. Given that there is already a stock
process in place it could be possible to replace components with extended versions
or altogether different ones. These replacements could be dependent upon some form
of pipeline definitions that will enable I/O in between the component connections
or rerouting through user components/pipelines.

Perhaps this could lead to having a number of pre-made replacement components
and pipelines that can be mixed and matched for more flexibility and particular
end purposes (localization, translation, authoring, ?)

Maybe this is a lot of work to implement in the short term, might be something to
consider as part of the toolkit's future evolution.

Don't know if you have seen it, but gstreamer (http://gstreamer.freedesktop.org)
is a good example of a pipelining application if you want to look at it.

Cheers.

Raymond




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com