<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<font style="" face="Tahoma">
</font><font style="" face="Tahoma">Hi, once more.<br><br>Doug Ewell</font><font style="" face="Tahoma">
</font><font style="" face="Tahoma"><a href="mailto:ietf-languages%40alvestrand.no?Subject=Re%3A%20New%20extension%20for%20transformed%20languages&In-Reply-To=%3C20120307085714.665a7a7059d7ee80bb4d670165c8327d.964f6c1265.wbe%40email03.secureserver.net%3E" title="New extension for transformed languages">doug at ewellic.org
</a></font><font style="" face="Tahoma"><br></font><font style="" face="Tahoma">
</font><font style="" face="Tahoma">Wed Mar 7 16:57:14 CET 2012</font>
<hr>
<pre>> CE Whitehead <cewcathar at hotmail dot com> wrote:
>>><i> Of course, some translation decisions have more to do with the
</i>>>><i> individual translator than with either the source or target language,
</i>>>><i> and of course there is no way to tag that thought process, nor should
</i>>>><i> there be.
</i>>><i>
</i>>><i> Then I suppose Doug does not feel it would not be wise to register a
</i>>><i> mechanism for a translation (I am unsure myself as to whether it would
</i>>><i> be wise, though, because, for example, some people translating poetry
</i>>><i> ignore the rhythm and carefully translate the words and then make the
</i>>><i> word order come out in the new language; other translations are just
</i>>><i> word-by-word without being rearranged; and then some translations take
</i>>><i> a great deal of liberty, perhaps trying to convey sentence rhythms, or
</i>>><i> the author's "voice").
</i>
> No, I don't feel it would be wise to register a mechanism for
> translation, because we have a brand-new extension ('t') that claims
> to be usable for just that purpose. There would have to be some
> demonstrated real-world need that the 't' extension demonstrably does
> not meet.
Agreed. But I met a second mechanism -- in addition to the m0 mechanism now available for use with the 't' extension).
> Some* decisions on the part of the translator are not taggable, IMHO.<br>This is what I was referring to, that you believe that what exactly the translator decided may not be taggable in more detail.<br>> That does not mean I disagree with the entire concept of tagging content
> as having been translated.<br>Glad to hear this. Thanks. Just to see a tag that it's a translation from language A to language B to me seems nice. (Though as noted translations vary; some are quite literal, word by word; some not; I guess this is what some have questioned but I think identifying both kinds of texts as translations is fine.<br><br>Best,<br>--C. E. Whitehead<br>cewcathar@hotmail.com<br>> --
> Doug Ewell | Thornton, Colorado, USA
<a href="http://www.ewellic.org/">http://www.ewellic.org</a> | @DougEwell
</pre> </div></body>
</html>