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

Can we simplify the trademark guidance? #145

Closed
ghost opened this issue Nov 24, 2020 · 8 comments
Closed

Can we simplify the trademark guidance? #145

ghost opened this issue Nov 24, 2020 · 8 comments
Labels
section-language an issue in the "Language" section

Comments

@ghost
Copy link

ghost commented Nov 24, 2020

https://documentation.suse.com/style/current/single-html/docu_styleguide/#sec-trademark asks writers to follow the rule to only use the trademarked version of a product name on its first occurrence within a chapter but not on later occurrences. This is problematic both because it prevents effective use of entities but also because it seems like unnecessary mental overhead. In practice, this results in our documentation being non-compliant with our own guidelines in most cases.

We should check with Legal if we can just remove all the trademark mentions. Our legalnotice also contains some language about trademarks, maybe we can expand that wording to say that we don't assume trademarks are ours etc. (Current language: "For SUSE trademarks, see https://www.suse.com/company/legal/. All other third party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of &suse; and its affiliates. Asterisks (*) denote third-party trademarks.")

Alternatively, we should probably make sure to use the appropriate trademark on all mentions of the trademarked word. That would still be a bit of a pita for writers but at least it would be consistent and easy to resolve with XML entities/Asciidoc attributes.

(via @KucharczykL )

@janajaeger
Copy link
Contributor

Given that it might take longer to clarify than adding the default option (with TM) to the entity definition, I'm with Stafan and Lukas.

@jfaltenbacher
Copy link
Contributor

I don't think we can leave out the trademarks entirely. I found this guidance https://www.inta.org/wp-content/uploads/public-files/resources/consumer/2020_TMUseMediaInternetPublishing.pdf

@dariavladykina
Copy link
Contributor

I'm strongly in favor of using trademarks on their first occurrence only.
There are entities like susereg and slereg (for SUSE® Linux Enterprise) and &trademark; for ™ in doc-kit.
We have guidance on how to use them and we provide info where to look them up. This seems enough to me.

@PadraigDillon1
Copy link

Does the issue still exist that in a modular doc world the first instance in one piece of content may not be the first location in another. Is there a way around that?

@janajaeger
Copy link
Contributor

Does the issue still exist that in a modular doc world the first instance in one piece of content may not be the first location in another. Is there a way around that?

No, there is no way of knowing which instance comes first. The only thing we can do is add the TM and friends for the first occurrence per file. A file could be the first in once article and come fourth in another. Although, if we managed to somehow squeeze all of the TMed terms into the info section of the assembly, we could use them there and keep the topics free of trademarks. But as we don't know whether this is possible for each and every term and article, we need to play safe and go by topic :(

@cwickert
Copy link
Member

Long story short: Let's stick to trademarking the first occurrence. Should cover most cases, even in modular docs.

@PadraigDillon1
Copy link

Response from Chioma Benjamin:
We don't need to use the (superscript) 'TM' symbol - the trade mark is effective without the TM symbol.

@PadraigDillon1
Copy link

Query on TM symbol.txt
Email exchange with Chioma Benjamin attached confirming no legal requirements for TM symbols.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
section-language an issue in the "Language" section
Projects
None yet
Development

No branches or pull requests

5 participants