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

List:       kde-devel
Subject:    Re: l10n error?
From:       Burkhard =?iso-8859-1?q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2008-08-26 4:32:02
Message-ID: 200808260632.02192.lueck () hube-lueck ! de
[Download RAW message or body]

Am Montag 25 August 2008 23:51:56 schrieb Matthew Woehlke:
> Burkhard Lück wrote:
> > Am Montag 25 August 2008 23:08:07 schrieb Albert Astals Cid:
> >> A Dilluns 25 Agost 2008, Matthew Woehlke va escriure:
> >>> I've been seeing this sort of message a lot in all builds I do:
> >>> No localization exists for "en" or "". Using default "en".
> >>> No "en" localization of "nav-up" exists.
> >>>
> >>> It seems to have appeared recently (within ~1-2 weeks), anyone know
> >>> what's up? Should I be worried?
> >>
> >> That's part of a change Burkhard Lück did to fix some untranslatable
> >> entities in documentation. As far as i know, it's not a problem, but i'm
> >> CC'ing him so he can confirm.
> >
> > Matthew, where do you get these error messages?
> > trunk / stable?
> > building a language?
> > or a kde module?
>
> trunk, and... basically everywhere (e.g. building kdelibs, kdebas,
> kdepim, etc). I also recently did a total purge of my KDE environment
> (rm -rf $KDEDIR; rm -rf $KDE_BUILD/*) so it's probably not a dirty-build
> problem.

Do you have errors like

share/apps/ksgmltools2/docbook/xsl/common/fr.xml:183: parser 
error : Entity 'nbsp' not defined

or

apps/ksgmltools2/docbook/xsl/common/sl.xml:183: parser 
error :?

in the logs?

-- 
Burkhard Lück
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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