Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we use British or US spelling of mitre? #259

Closed
MPBailey opened this issue Jan 23, 2023 · 2 comments
Closed

Should we use British or US spelling of mitre? #259

MPBailey opened this issue Jan 23, 2023 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@MPBailey
Copy link
Collaborator

This was triggered by noticing that the current WG8 doc on the next cycle of errata uses the UK 'mitre' spelling for the title of 8.4.3.5 and the body of that clause uses the US 'miter'. In fact 32000-2 uses 'miter' throughout (the writer of the errata doc must have been tripped up by not being American!)

I can't find anywhere that the word is used in constructing a PDF file; it's always abbreviated to something like 'ML' for mitre limit. But the back-reference to PostScript in table A.1 does note the use of 'setmiterlimit' there.

In general we follow the ISO guidance on using British English spelling except where that would invalidate PDF files conforming to pre-ISO specifications. Not sure this one is worth changing, but figured I should ask.

@MPBailey MPBailey added the bug Something isn't working label Jan 23, 2023
@petervwyatt petervwyatt added documentation Improvements or additions to documentation and removed bug Something isn't working labels Jan 23, 2023
@petervwyatt
Copy link
Member

Similar to the use of "colour" in prose, but "color" for the technical key names and values, etc.

Maybe can resolve now with a generic editor note as a reminder for fixing in the future, or just leave alone (park) as I'm sure there are other similar issues...

@petervwyatt
Copy link
Member

Only technical wording is the PS "setmiterlimit" - everywhere else (27!) is descriptive. ML is the key.

PDF TWG agree

petervwyatt added a commit that referenced this issue Jan 27, 2023
As editor note
@petervwyatt petervwyatt self-assigned this Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants