| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Adding the xml:lang attribute for XNL and Docbook output
Interesting links:
- language codes (different from country codes!): https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
- example for xml.xsd: http://www.java2s.com/Code/XML/XML-Schema/importanotherXMLschema.htm
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Due to a regression on #7061 travis showed message:
```
not ok 71 - [071_enum_in_anon_ns.cpp]: test that enum values in anonymous namespaces produce no warning
-------------------------------------
/home/travis/build/doxygen/doxygen/testing/071/namespace_a_namespace_1_1_0d0.xml absent
-------------------------------------
```
|
| |
|
|
| |
In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
|
| | |
|
|
|
When a C++11 `enum class` was present in an anonymous namespace (usually
in *.cpp files), the XML output was emitting warnings similar to the
following:
Internal inconsistency: member False does not belong to any container!
And the XML output was rendering bogus IDs for enum values starting with
`dummy_`, such as:
dummy_1a96ab6574751fdf6a53ceec8a3896c45daf8320b26d30ab433c5a54546d21f414c
The fix is to call memberOutputFileBase() on the enumeration itself and
not on the enum value, that way it provides correct file base that
corresponds to file base of the enumeration. There's also a new test
that checks this.
Note: this assumes that enum values belong to the same compound as enums
themselves. In my experience that was always the case and there's no
broken test after this change, so I hope I didn't break anything.
|
