Have there been any progress in this matter?

On Jun 8, 11:09 pm, Jack Killpatrick <j...@ihwy.com> wrote:
> Hi,
>
> I considered building something like that in, but decided I didn't know
> enough about other languages to decide how best to handle them. Thanks
> for starting the dialog. Does anyone else have any opinion on this?
>
> The main thing I'm wondering is whether collecting them all under one
> nav item would, in some cases, result in *many* things ending up there
> and not many things left under the individual letters (depends on how
> many items start with these kinds of chars).
>
> Also, I think that # would mean "starts with a number" to most people,
> but numbers are already handled via the optional [0-9] nav item. If not
> #, then what else might make sense?
>
> On a related note: does anyone know offhand if high ascii chars like
> these can be used as CSS class names? I haven't ventured into
> researching that yet.
>
> Thanks,
> Jack
>
>
>
> Dave wrote:
> > Hi
>
> > In the example below there are non ascii characters, and as it is now
> > listmenu just ignores them. Maybe a solution could be to collect them
> > under a "#" tab.
>
> > <ul id="ulSec_LM_List">
> >         <li><a href="#">Agilityhunden</a></li>
> >         <li><a href="#">Aktivitetsbollen</a></li>
> >         <li><a href="#">BIO Shampoo</a></li>
> >         <li><a href="#">Oxsvans</a></li>
> >         <li><a href="#">Pipleksak - Groda</a></li>
> >         <li><a href="#">Vovex Balsam</a></li>
> >         <li><a href="#">Ädelsten</a></li>
> >         <li><a href="#">&Ouml;gonsten</a></li>
> > </ul>
>
> > Cheers- Hide quoted text -
>
> - Show quoted text -

Reply via email to