[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Request for naming advice
From:       Marta Rybczynska <rybczynska () gmail ! com>
Date:       2012-07-05 9:30:14
Message-ID: CAApg2=RSZbFXnNaT__7nL6TFMMpU+uDem8cXDQ66jpReCFsMAw () mail ! gmail ! com
[Download RAW message or body]

On Tue, Jul 3, 2012 at 4:25 PM, Martin Schlander <martin.schlander@gmail.com
> wrote:

>
>
> Legacy is definitely hard to translate, but it's pretty widely used after
> all,
> and I can't think of any better suggestion. Except possibly "deprecated" or
> "obsolete", not 100% sure if those would fit.
>

It's hard to translate, definitely. We're using an equivalent of "old" to
make it easier
for non-technical users to understand.

Marta

[Attachment #3 (text/html)]

<br><br><div class="gmail_quote">On Tue, Jul 3, 2012 at 4:25 PM, Martin Schlander \
<span dir="ltr">&lt;<a href="mailto:martin.schlander@gmail.com" \
target="_blank">martin.schlander@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="im">
<br>
</div><br>Legacy is definitely hard to translate, but it&#39;s pretty widely used \
after all,<br> and I can&#39;t think of any better suggestion. Except possibly \
&quot;deprecated&quot; or<br> &quot;obsolete&quot;, not 100% sure if those would \
fit.<br> </blockquote></div><br>It&#39;s hard to translate, definitely. We&#39;re \
using an equivalent of &quot;old&quot; to make it easier<br>for non-technical users \
to understand.<br><br>Marta <br>



[prev in list] [next in list] [prev in thread] [next in thread]