Re: [PHP-DOC] entities proposal
I myself would like to see some more entities :-) In the constanst.xml there are a lot of links to integer-types, e.g. /refernce/curl/constansts.xml like: link linkend=language.types.integerinteger/link For this it would be convinient to have an entity, also for other links to language.types. Opinions? There used to be an option, using typeinteger/type which is not the right to use in these cases for some reason. Ah, I forgot this possibility! Hm, I can't think of any reason, why not to use typeinteger/type. In /language/types.xml it is used this way and correctly renderd by the dsl-sheets (html-common.dsl)line 160: ;; Linking types to the correct place ... One difference: typeinteger/type: the resulting link is bold, while link linkend=language.types.integerinteger/link is normal. Is this the reason not to use the short notation? :-( BTW.: whats the reason for rendering typeinteger/type bold? According to tdg type is allowed in entry, term http://www.docbook.org/tdg/en/html/type-x.html Maybe because type tags are also used in prototypes on function pages[?], I don't know. As I understand the dsl-sheets the only difference is, these types are not linked. Friedhelm
Re: [PHP-DOC] entities proposal
Hm, I can't think of any reason, why not to use typeinteger/type. In /language/types.xml it is used this way and correctly renderd by the dsl-sheets (html-common.dsl)line 160: ;; Linking types to the correct place ... One difference: typeinteger/type: the resulting link is bold, while link linkend=language.types.integerinteger/link is normal. Is this the reason not to use the short notation? :-( BTW.: whats the reason for rendering typeinteger/type bold? I myself have no problems with bold. So we can use typeinteger/type as it seems. Goba
Re: [PHP-DOC] entities proposal
I myself would like to see some more entities :-) In the constanst.xml there are a lot of links to integer-types, e.g. /refernce/curl/constansts.xml like: link linkend=language.types.integerinteger/link For this it would be convinient to have an entity, also for other links to language.types. Opinions? There used to be an option, using typeinteger/type which is not the right to use in these cases for some reason. Maybe because type tags are also used in prototypes on function pages[?], I don't know. Goba
[PHP-DOC] entities proposal
Hi I myself would like to see some more entities :-) In the constanst.xml there are a lot of links to integer-types, e.g. /refernce/curl/constansts.xml like: link linkend=language.types.integerinteger/link For this it would be convinient to have an entity, also for other links to language.types. Opinions? Friedhelm
