[bt-devel] Doc fixed font note in handbook

[Martin Gruner]

Looks good!
Actually, an iso10646-1 is not always needed. If the text to display is in th 
iso8859-7 area, choosing a iso8859-7 font for the unicode font will be fine, 
since QT converts anything to iso10646-1 internally. But if one wanted to 
display not only text from one of the foreign iso8859-x subsets, one has to 
have a iso10646-1 font.

Martin

P.S. iso rules. ;)


> I the font information in the handbook last night changed this last night
> (but forgot to committ) to read:
>
> <section id="hdbk-config-bt-Unicode"><title>Unicode Fonts
> (ISO10646)</title> <para>Recent &Linux; distributions have Unicode support;
> however, only a minimal set of unicode
> fonts are provided with Linux Distributions.  The most useful of these
> fonts is clearlyu.  Some
> of the Sword modules have unicode encoding, most of these modules will
> display correctly
> with the fonts supplied in your distribution.</para>
> <para>If the module you wish to display is parsed
> in the display window as ??????????????????????? you you have encountered
> font trouble. either
> you are trying to display a module encoded in Unicode with a font that does
> not support unicode,
> or the particular unicode font you have selected does not contain the
> characters you need.</para>
>
> and so on
>
> It is on the CVS now.  How does this look.
>
> Martin Gruner wrote:
> > "Unicode fonts have not been included in any of the distributions (as of
> > January 2002)"
> >
> > I don't think that is right. SuSE has clearlyu for example. Users can
> > find out about the module's encoding in the "about module" dialog. There
> > is a little typo on this page too: "The $bibletime; team expects the Qt
> > problem to be resolved with the release of Qt3."
> >
> > Apart from that, your docs are getting better and better! Your're doing a
> > grand job!
> >
> > Martin