Testing the EBN

[Burkhard Lück]

Am Dienstag, 10. August 2010, um 18:21:39 schrieb Jeremy Whiting:
> On Tue, Aug 10, 2010 at 10:08 AM, Burkhard Lück <lueck at hube-lueck.de> wrote:
> > Am Dienstag, 10. August 2010, um 16:53:49 schrieb Allen Winter:
> > > On Friday 06 August 2010 4:11:24 pm Burkhard Lück wrote:
> > > > Am Freitag, 6. August 2010, um 21:59:25 schrieb Allen Winter:
> > > > > Howdy,
> > > > > 
> > > > > I'm trying to put the EBN back together.
> > > > > 
> > > > > I think the Krazy and APIDOX checking is operational.
> > > > > I know that the Docs Sanitizer tool is still out-of-service.
> > > > 
> > > > I'd really appreciate to get the doc sanitizer back ...
> > > 
> > > The doc sanitizer should be operational again.
> > > http://www.englishbreakfastnetwork.org/sanitizer
> > 
> > Thanks a lot for get that running again.
> > 
> > One issue I noticed in
> > reports/kde-4.x/kdeaccessibility/jovie/index.html
> > "Entity 'jovie' not defined"
> > 
> > But kdelibs has
> > general.entities:161:<!ENTITY jovie  "<application>Jovie</application>">
> 
> I noticed that before ebn went down too I think.  Did I do that wrong? do
> most applications define their entity in their own docbook? or in
> general.entities?
> 
1) Entity in docbook header: it can only be used in this documentation and is 
untranslatable

2) Entity in general.entities: it can be used in any docbook and is 
untranslatable.
The application+documentation depends on the kdelibs version when the entrity 
was introduced to general.entities.

3) Entity in en|[lang]user.entities: it can be used in any docbook and is 
translatable.
The application+documentation depends on the kdelibs version when the last 
entrity was introduced to en|[lang]user.entities.

1) and 2) are really problematic for every application not in the kde main 
modules like extragear + playground applications,

-- 
Burkhard Lück