Re: sgml-id / xml-id and namespaces

Am 23.12.2009 14:23, schrieb David Nečas:
> On Wed, Dec 23, 2009 at 12:54:54PM +0100, Nicola Fontana wrote:
>>> But this does not solve the type/section clash, does it?
>> Yes, it will: the section is nothing more than a root subsection. The
>> problem is the final file name should be treated specially (as I think
>> nobody would like "DOC:::GtkWidget.html" or something similar), but I
>> guess the file name is yet handled apart.
> I thought most people expect #GtkWidget to lead to the section, not to
> the struct definition (that usually does not contain anything useful).
> That is if a type has a section on its own, #type should lead to the
> section; it should lead to the struct definition only if it's an
> auxiliary type without a top-level section.
> So you suggest to write #GtkWidget to link to the section and
> #GtkWidget-with-some-suffix-or-prefix to the struct, but the XML ids
> being exactly opposite, i.e GtkWidget-compilicated for sections and
> GtkWidget for the struct?  Does it makes sense?
> Yeti

We can easily make it so that:
- #Gtkwidget -> DOC--GtkWidget
- ->

and there should be the fallback to do
- #Gtkwidget -> GtkWidget
if there is no DOC--GtkWidget. This would handle the case where one has multiple
structs in one section (the section-id would be more generic).


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]