XMLSpy pretty-print rules impacting the papiNet-API.yaml 4-0-0

[PetterThy]

When opening pretty-print in XML Spy it causes the comments to move to a separate line.
Patrice has raised issue towards Altova.

[patricekrakow]

As suggested by @MrNordenberg, we could make a version 3.0.1 which would be identical as 3.0.0 but only have the papiNet-API.yaml with the XMLSpy pretty-print.

[patricekrakow]

We also need to check the behavior of the YAML Pretty Printing of Altova XMLSpy 2026, it seems that there is now a new configuration option:

• "Use Single Quotes": If selected, converts all quotes to single quotes.

which should be useful. But we do not see anything about the comments being put on their own line.

[patricekrakow]

I have posted a question on the Altova user form: https://www.altova.com/Forum/default.aspx?g=posts&t=1100005299

[patricekrakow]

We have received an answer from "K101" (who seems to be from Altova): "Both appear to be reasonable feature requests. I recommend you contact Altova Support directly to request them."
@PetterThy, could you do that?

Now, we have to decide if we adopt the current XMLSpy pretty-print rules forever, or we keep our current style, hoping that Altova will implement our "reasonable feature requests".

If we go for the second option, we should write our own linter that would reverse the two problematic XMLSpy pretty-print rules, but it might not be that easy... let's discuss that topic.

[larsolofsson]

I tested some pretty print in XMLSpy 2026. My findings

        - SheetfedOffset
          - SilkScreen
          # pretty print?
          - WebOffset
      test: # pretty print?
        type: string
        # pretty print?
      basisWeight: # This is the result of a nice compromise between EU and US usage.
        type: object
        # pretty print?
        unevaluatedProperties: false
        # pretty print?
        required: # pretty print?
          - value
          # pretty print?
          - uom

Inline comment for a property stays on line, see properties test and basisweight
Inline comment for type of a property is moved to a new line, see types string and object.
Inline comment for unevaluatedProperties: false is moved to a new line.
Inline comment for required: stays on the line but for -value in required it is moved to a new line
Inline comments for enumeratiuons are moved to a new line, see - SilkScreen

Why is it different depending on items?
Is it a bug in XMLSpy or is it designed to work like this?

[larsolofsson]

I think that papiNet doesn't need to add a version 3.0.1
Most of the inline comments are removed so number of changes are still the same for these comments.
Some single quotes are changed to double quotes, but these changes are not many compared to all other changes.