[dbdoclet] Re: html2db: feature request - indexterm handling
- From: Micki Kaufman <micki001@xxxxxxxxxxxxxx>
- To: dbdoclet@xxxxxxxxxxxxx
- Date: Wed, 7 Jan 2004 11:06:00 -0500
Dear Michael:
I like that solution.
In thinking about it, I believe the nesting of primary, secondary,
and tertiary would remain unaffected.
Thanks,
Micki
At 10:22 AM +0100 1/7/04, Michael Fuchs wrote:
>=2D----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi Micki,
>
>unfortunatly you can not use the id attribute for this purpose, because it=
>=20
>must be a unique id for a single element. If you use the example machanism=
>,=20
>you have to define a name like "example_this_special_example". This was don=
>e=20
>to separate formal from informal examples (I wouldn't do this again). But I=
>=20
>don't think that this would be a good solution for indexterm.
>
>A possible solution could be to put all the information into the title=20
>attribute, e.g. title=3D"index_primary:Font Size".
>
>Bye
> Michael
--
Micki
mailto:micki001@xxxxxxxxxxxxxx
- References:
- [dbdoclet] html2db: feature request - indexterm handling
- From: Micki Kaufman
- [dbdoclet] Re: html2db: feature request - indexterm handling
- From: Michael Fuchs
Other related posts:
- » [dbdoclet] html2db: feature request - indexterm handling
- » [dbdoclet] Re: html2db: feature request - indexterm handling
- » [dbdoclet] Re: html2db: feature request - indexterm handling
- [dbdoclet] html2db: feature request - indexterm handling
- From: Micki Kaufman
- [dbdoclet] Re: html2db: feature request - indexterm handling
- From: Michael Fuchs