To me, those examples have nothing to do with domain or style. They can be
solved in better general ways with a mix of CG, semantics, and lexical
selection. And I know this, 'cause it's what our non-Apertium closed-source
translation engine uses.
For example, the English text
"The key to the piano will let you unlock it and hit the keys of the
piano which are in harmonic key."
translates into Danish as
"Nøglen til klaveret vil lade dig låse det op og trykke på tasterne af
klaveret som er i harmonisk toneart."
In this example, the differences are resolved during lexical selection.
We have a total of 2 domains, for cases where the same word in the same
context truly means something entirely different. Introducing many tiny
domains is counterproductive when you could instead solve it in a general
way that will benefit all domains.
Don't lock away good translations in domains when it's clearly not needed.
-- Tino Didriksen
On Sun, Dec 16, 2012 at 2:21 PM, Per Tunedal <[email protected]>wrote:
> Consider e.g. the
> example of translating the English word "key", or similarly the French
> word "clé/clef", to Swedish. If the domain is e.g.
> Tourism/accommodation/real estate or similar, the word would most likely
> translate to "nyckel" (to lock/unlock the door of a house). On the other
> hand if the domain is e.g. information technology (or even music) the
> word would most likely translate to "tangent" (on your keyboard or
> piano).
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
