Skip to content

Content Modifiers : case insensitive ? #1228

@JBoisseau-ByDeluxe

Description

@JBoisseau-ByDeluxe

Content modifiers are defined with a specific capitalisation : Temp,[Luminance]fL, DVIs ..

Actual CTTs regularly divert from the example:
Temp -> temp (sometimes)
[Luminance]fL -> [Luminance]FL (always)
DVIs -> Dvis (sometimes)

NB:
the webpage says [Luminance]fL
while the registry says [Luminance]fl

I wonder if we should:
A- assume a tolerance on the capitalisation for all Content Modifiers
B- keep as is (enforced capitalisation), but only fix the Luminance to "FL", uppercase

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions