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

List:       kde-i18n-doc
Subject:    Re: usage of &kappname; in documentation
From:       Luciano Montanaro <mikelima () gmail ! com>
Date:       2009-02-25 10:38:03
Message-ID: b2289f80902250238i8311b29n26a87425dcf4b101 () mail ! gmail ! com
[Download RAW message or body]

On Wed, Feb 25, 2009 at 2:04 AM, Chusslove Illich <caslav.ilic@gmx.net> wrote:

> There's no problem with AppName -> &something;, so long as that &something;
> reflects the AppName (less importantly), and changes whenever the AppName
> itself changes (more importantly).

If it has to change whenever the application name changes, what's the
point in using an entity?

>
>> So you think it would be best from the translator's point of view to get
>> rid of these entities completely?
>
> Of generic &kappname; entities? Yes.

That's unforunate, they are pretty handy for languages where this
isn't an issue (The &kappname; Manual tranlation could be unfuzzied
with a click instead of translated over and over). But if the problems
are more than the advantages, let it go.

Isn't it possible to use the cool scripting technology to solve this problem?

Luciano

-- 
Luciano Montanaro

Anyone who is capable of getting themselves made President should on
no account be allowed to do the job. -- Douglas Adams
[prev in list] [next in list] [prev in thread] [next in thread]