Allow othername & lineage #83
Comments
|
Toms yesterday made me aware that DocBook also supports the <givenname/> element. I think we should try to remove <firstname/> in favor of <givenname/>, since the latter is globally more applicable than the Western-centric <firstname/> element. |
|
Removing |
In regards to personname: * Allow othername, honorifc, linage * Restore content model of personname to not mix firstname with givenname
In regards to personname: * Allow othername, honorifc, linage * Restore content model of personname to not mix firstname with givenname
|
If we still operate under the assumption that people have GeekoDoc v1 and v2 installed side by side, I think this might be a compatibility break worth making -- people would explicitly update to the new schema and it would be expected that there may be a few minor issues like this. No? |
|
Good point. In that sense, a major release could introduce a compatibility break. The question is if it's worth. After I've looked into the doc-sle repo, it isn't not that much: I've counted 16 files which contains firstname. So it seems manageable... Let me think about it. |
In regards to personname: * Allow givenname, othername, honorifc, and linage * Restore content model of personname to not mix firstname with givenname
|
The major repo where the tag is relevant is going to be the SBP repo, I guess. But that largely uses plain DocBook because the documents there are incompatible for a number of reasons. |
ghost
mentioned this issue
|
Effort is probably low, could add the other tags. |
Within <personname/>s, currently only <firstname/> & <surname/> are allowed. However, a bunch of people legitimately do have middle names or Jr./Sr. added to their name. Hence, <othername/> and <lineage/> should probably be allowed. (AsciiDoctor also tends to generate those tags.)
Should I ever have argued for the opposite, please ignore my past opinions. :)
The text was updated successfully, but these errors were encountered: