"text-case" attribute not applied to "locator" variable

edited January 4, 2021
With the MWE below, a locator set to "iv" will be rendered as "iv", not "IV". However the bibliography macro shows that text-case is taken into account with other variables.

This bug affects both the Style Editor and LibreOffice Plugin.

  • You need to wrap XML in <code> tags or post to pastebin, github or the like
  • Sorry, I was posting it to pastebin when you answered! Here it is:

    <?xml version="1.0" encoding="utf-8"?>

    <style xmlns="http://purl.org/net/xbiblio/csl"; class="note" default-locale="en-US" version="1.0">
    <title>Minimal example with text-case on locator</title>
    <category citation-format="note"/>
    <category field="history"/>
    <rights license="http://creativecommons.org/licenses/by-sa/3.0/">This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 License</rights>

    <layout suffix=".">
    <text variable="locator" text-case="uppercase"/>

    <text variable="title" text-case="uppercase"/>

  • edited January 4, 2021
    That's specific to roman numerals I think -- not sure exactly what the processor does, but I think it recognizes iv as a Roman 4 and then doesn't apply text casing. If you use e.g. "au" it will uppercase. What's the usecase?
  • Mostly for volume numbers.
  • It's a little strange, on the one side because the "font-variant" attribute is applied, and in the other side because even a "number" element can carry a "text-case" attribute.

    It's not dramatic for I can type "IV" in the locator field, what would be bothering only if I had to switch to a style which requires volume numbers in small caps—I admit it's quite an edge case. But I thought it was worth mentioning, since this handling doesn't conform to the specification.
  • yeah, I don't think it's right.
    <number variable="locator" form="roman" text-case="uppercase"/>
    produces IV with a 4 as a locator, so apart from not being spec, I also can't make out a consistent behavior.
  • Yeah this looks like a bug to me
  • Fix applied in processor tag 1.4.61
Sign In or Register to comment.