[Koha-devel] Re: HTML files Summary: Expires:

[acli@ada.dhs.org via news-to-mail gateway]

Hi,

In article <20030122014823.GA20359 at beastie.bofh.dk>, Bobby
Billingsley <koha-devel at lists.sourceforge.net> wrote:

>Wednesday d. 22. January 2003 skrev Rachel Hamilton-Williams:
>
>> Personally I think it's a good idea - but the people
>> translating are perhaps in a better position to know?
>
>I'll go along with the symbolic rather than the numeric
>entities for now then and see if there's any outcry ;)

I think we all want symbolic :-)

(or like Benedict or myself [when I type Chinese] just type it
in whatever charset the page is supposed to be in)

perhaps until we hit a language where there are no symbolic
entity names. Perhaps Maori might need to use numeric? Some
(all?) Maori pages seem to use numeric.

>> How "style type"?
>>
>> IF you mean font tags beign converted to <h1> etc tags then
>> great
>>
>> I suspect we're not ready for positioning Div tags - or
>> we will need to start having different template sets for
>> different browsers
>
>Well, there seems to be some disagreement on this - I concur
>with Ambrose's argument that not all browsers can handle CSS
>stuff and with discussions on #koha that graceful degradation
>is a nice thing, but as Chris suggests in his mail (below),
>using the templates combined w. user preferences in the DB
>could probably achieve "the best of both worlds". However I can
>also see that this might prove to be more intensive in upkeep
>(more stuff to maintain/ translate/develop). As it stands now I
>feel that leaving off CSS stuff for the time being is probably
>the way forward.

Since I haven't used HTML tidy myself, I don't know how far it
will go. (I am definitely against HTML 4.0x "Strict"; if we go
that far we might as well go further & use ISO 15445 :-)

My only concern is that if it converts B and U tags into SPAN
(or both B and U into EM), under a text browser the emphasized
elements will lose their emphasis (or difference in emphasis),
and we end up having something worse than before. In Koha there
are some screens that rely on certain things being, e.g., bold
(such as mandatory fields in the MARC editor).

I.e., if HTML tidy does not actually go too far (i.e., it
preserves B, U, H1, etc.), the resulting HTML+CSS pages will
automatically degrade gracefully, and we won't need to split the
templates into "graphical" and "text" versions unless we really
want to.

Or we could check all the Koha screens with a text browser and
see if there are different kinds of emphasized elements. We
can then run HTML tidy on one such screen and see if it has
any adverse impact.


-- 
Ambrose LI Cheuk-Wing  <a.c.li at ieee.org>