Re: [Koha-devel] HTML files

[Bobby Billingsley]

Hej Team ...

Wednesday d. 22. January 2003 skrev Rachel Hamilton-Williams:

> Hi
> 
> > The main thing is that it croaks on the HTML::Tidy tags, even when
> > configuring it to accept these tags. The solution to this would be to
> > re-write these tags as
> 
> Is that HTML::Template tags?

Ahh - yup - my bad ;)

> >  <!-- TMPL_VAR NAME='blargh' -->
> > 
> > rather than
> > 
> >  <TMPL_VAR NAME="BLARGH">
> > 
> > ...this will also produce well-formed HTML which (to me at least) seems
> > like a good idea.
> 
> I've no idea if you can do that - I'd assume that it wouldn't work - that 
> html::template wouldn't parse it properly?  But perhaps someone else can help 
> with that.

According to the docs on HTML::Template it should be fine - need to
double-check that though. I'll do that on my own installation.

> > Another issue is when using non-ascii characters I'd prefer to use entities
> > like "&egrave;" rather then "&#232;" but am not sure what the general
> > consensus on this is.
> 
> 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 ;)

> > Also, the tidy program seems to do a nice job of converting style-type tags
> > into style properties/CSS - is this desireable?
> 
> 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.

On Wed, 22 Jan 2003, Chris Cormack wrote:

> > >Also, the tidy program seems to do a nice job of converting
> > >style-type tags into style properties/CSS - is this desireable?
> >
> > My personal opinion is that this is only partly desirable. Part
> > of an open-source OPAC's strengths is that it can be run on a
> > text browser. If we drop all "style-type" tags, we lose B, U,
> > INS, DEL, HR, etc. (tags that can degrade gracefully on a text
> > browser); CSS styles can't be trusted to do all the tasks we
> > assume they can do.
> >
> > If Koha does not use B, U, INS, DEL, or HR, I guess converting
> > the style-type tags to CSS is then indeed desirable.
> >
> Hi Guys
>
> I think what we can do is both :-) Thats where the themes come in.
> IE each set of templates lives in theme/language
>
> So we could have a textonly/en/  or textonly/dk  for the text based browsers.
> And fancy styles etc for others?


/bobby

-- -- -- -- -- -- -- Bobby Billingsley, General Specialist -- -- -- -- -- -- --
 ___    .--.- \   |                                 |                        _ 
`-,_`--'__/ x./_  | Remember to love while you dare | ASCII ribbon campaign ( )
//-_`--/    //\ \ | remember to live while you do   |  - against HTML email  X 
 \__/  `---' \__/ |                   -- Piet Hein  |              & vcards / \
                 Lat: 55° 40' 52" N Lon: 12° 32' 56" E 
     Anyone without a sense of humor is at the mercy of the rest of us :->