Subject: Re: [xsl] Joining sibling elements From: JBryant@xxxxxxxxx Date: Wed, 10 Aug 2005 16:26:06 -0500 |
Hi, Joris, I was referring to people translating documents in languages like English and Dutch for other people to read (I think that's what Marcin meant in her query). I have sent a much longer response to your private address, since it wandered so far off topic. Jay Bryant Bryant Communication Services (presently consulting at Synergistic Solution Technologies) "Joris Gillis" <roac@xxxxxxxxxx> 08/10/2005 03:16 PM Please respond to xsl-list@xxxxxxxxxxxxxxxxxxxxxx To xsl-list@xxxxxxxxxxxxxxxxxxxxxx cc Subject Re: [xsl] Joining sibling elements Hi Jay, Tempore 22:11:45, die 08/10/2005 AD, hinc in xsl-list@xxxxxxxxxxxxxxxxxxxxxx scripsit <JBryant@xxxxxxxxx>: > Basically, you get better > translation results if the translators can work on large blocks of > uninterrupted text. Lots of elements break up the text, which makes it > harder for the translators to follow the meaning and properly translate. > Even experienced, knowledgeable translators who have been trained about > which elements to ignore have trouble with this, as it's human nature to > try to make sense of what we see. Of course, the translators may also > inadvertently mangle the elements, too, but that doesn't hinder their > translation process. I'm not sure if I'm following. Are we speaking here about - translation of natural languages? (e.g. Dutch -> English) - human or computer translators? I'm puzzled, really... -- Joris Gillis (http://users.telenet.be/root-jg/me.html) Vincit omnia simplicitas Keep it simple
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Joining sibling elements, Joris Gillis | Thread | Re: [xsl] Joining sibling elements, Marcin Miłkowski |
[xsl] Problems matching end-of-line, Kenneth Stephen | Date | Re: [xsl] Joining sibling elements, JBryant |
Month |