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

List:       kde-i18n-doc
Subject:    Re: backwards compatibility for docbook entities
From:       Robby Stephenson <robby () periapsis ! org>
Date:       2012-12-23 1:05:39
Message-ID: 50D658E3.8090407 () periapsis ! org
[Download RAW message or body]

Freek de Kruijf wrote:
> Op donderdag 20 december 2012 22:35:57 schreef Robby Stephenson:
>
>> What's the best way to handle backwards compatibility when new XML
>> entities are added to translated documentation? Tellico has some issues
>> compiling with older versions of KDE (4.5, I think) because of
>> translator entities.
>>
>> [ 12%] Generating index.cache.bz2
>> index.docbook:70: parser error : Entity 'Freek.de.Kruijf' not defined
>> &Freek.de.Kruijf;<othercredit role="translator"
>>                   ^
>> index.docbook:293: parser error : Entity 'vertaling.freek' not defined
>> &meld.fouten;&vertaling.freek;
>>
>> Is there a way to gracefully handle this situation? I've basically just
>> been telling users to edit the CMakeLists.txt file and remove whichever
>> translations are causing the problems. I'm thinking of something like a
>> preprocessor statement in C++ where I can wrap the entity in a version
>> check...
>>
>> Thanks!
>> Robby
>
> In my view, you should back port the files with these entities from a higher
> version of KDE. AFAIK there are only additions to the entities and some may
> have changed values (i.e. a new email address).

So you're saying that the updated nl/user.entities file should be 
backported to older versions of KDE, like 4.5 or 4.6? But those are no 
longer being released so it doesn't really fix the issue.

Is there any conditional check I could put in Tellico such that recent 
docbook entities don't cause a compilation failure? Perhaps I copy the 
entities into a custom file that somehow only gets included in the 
docbook generation for older KDE versions. I just don't know how to do that.

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