[jQuery] Re: listmenu plugin: non-ascii characters
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 lia href=#Agilityhunden/a/li lia href=#Aktivitetsbollen/a/li lia href=#BIO Shampoo/a/li lia href=#Oxsvans/a/li lia href=#Pipleksak - Groda/a/li lia href=#Vovex Balsam/a/li lia href=#Ädelsten/a/li lia href=#Ouml;gonsten/a/li /ul Cheers- Hide quoted text - - Show quoted text -
[jQuery] Re: listmenu plugin: non-ascii characters
Hi Dave, I have a few things penciled out to add to the plugin, but haven't had a chance to get to them yet. I have your email from a while ago with the mockup of your idea ( http://img266.imageshack.us/img266/618/listmenuz.png ), thanks very much for that, it seems like a good approach. Thanks, Jack Dave wrote: 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 lia href=#Agilityhunden/a/li lia href=#Aktivitetsbollen/a/li lia href=#BIO Shampoo/a/li lia href=#Oxsvans/a/li lia href=#Pipleksak - Groda/a/li lia href=#Vovex Balsam/a/li lia href=#Ädelsten/a/li lia href=#Ouml;gonsten/a/li /ul Cheers- Hide quoted text - - Show quoted text -
[jQuery] Re: listmenu plugin: non-ascii characters
Nice, looking forward to it. Cheers, Dave On Jul 8, 2:35 pm, Dave messedupp...@gmail.com wrote: 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 lia href=#Agilityhunden/a/li lia href=#Aktivitetsbollen/a/li lia href=#BIO Shampoo/a/li lia href=#Oxsvans/a/li lia href=#Pipleksak - Groda/a/li lia href=#Vovex Balsam/a/li lia href=#Ädelsten/a/li lia href=#Ouml;gonsten/a/li /ul Cheers- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] Re: listmenu plugin: non-ascii characters
Hi Here is an idea. Made an image to illustrate it. http://img266.imageshack.us/img266/618/listmenuz.png By adding two options like, includeNonAscii: true|false and nonAsciiMenuType: hover|static. As default includeNonAscii is false and things works as it does now. If includeNonAscii is true, then collect all these characters in a second array. If nonAsciiMenuType is hover the submenu with these characters will be shown when hovering the ... tab. If nonAsciiMenuType is static then the submenu will be static under the main menu. 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 lia href=#Agilityhunden/a/li lia href=#Aktivitetsbollen/a/li lia href=#BIO Shampoo/a/li lia href=#Oxsvans/a/li lia href=#Pipleksak - Groda/a/li lia href=#Vovex Balsam/a/li lia href=#Ädelsten/a/li lia href=#Ouml;gonsten/a/li /ul Cheers- Hide quoted text - - Show quoted text -
[jQuery] Re: listmenu plugin: non-ascii characters
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 lia href=#Agilityhunden/a/li lia href=#Aktivitetsbollen/a/li lia href=#BIO Shampoo/a/li lia href=#Oxsvans/a/li lia href=#Pipleksak - Groda/a/li lia href=#Vovex Balsam/a/li lia href=#Ädelsten/a/li lia href=#Ouml;gonsten/a/li /ul Cheers
