> > Just mention that the main problem that I found when working on the iOS
> > prototype was the fact that there were several duplicated symbols. For
> > instance, each program (ltproc, interchunk, postchunk and so on) has
> > logically a main function but, since iOS apps must consist of a single
> > executable, their names collide when putting them together. The solution
> > that I adopted was simply to rename them. Because of that, I sort of
> > hardcoded the pipeline for a single language pair, using temporary files
> to
> > communicate between the different stages of the translation. And, as I
> said
> > before, the transfer stage wasn't working, but I couldn't find out why.
> As
> > for the dependencies, I simply compile them targeting iOS and link
> > statically, and it worked.
> >
>
> If you're going to look at that again, you should really take a look
> at apertium-service. Pasquale already solved the problem of joining
> together the various components into a single application, and the
> service part was designed to be pluggable, so it shouldn't be too hard
> to rip it out.
>
>
I didn't know about it, but it seems that it can be very useful. Thank you!
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
