Bug 8428 - ThinLinc component names are inconsistent in how they are capitalized
Summary: ThinLinc component names are inconsistent in how they are capitalized
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on: 8440
Blocks:
  Show dependency treegraph
 
Reported: 2024-10-02 13:54 CEST by William Sjöblom
Modified: 2024-11-04 10:30 CET (History)
2 users (show)

See Also:
Acceptance Criteria:


Attachments

Description William Sjöblom cendio 2024-10-02 13:54:52 CEST
Some components, for example ThinLinc Desktop Customizer and Client Customizer are consistently written in "Title Case" in the documentation.

Other components, such as ThinLinc Web Administration, is sometimes written as "ThinLinc Web Administration" and other times as "ThinLinc web administration". "ThinLinc Client/client" is also in this group.

All while some components always written in "sentence case". I didn't bother finding any examples here, but there probably are some.

It'll probably be hard to find some universal rule here, but we should at least try to be consistent.
Comment 1 William Sjöblom cendio 2024-10-02 14:00:23 CEST
To not sound like <insert trendy American company with a massive marketing budget>, I would prefer to use sentence case as much as possible. There are of course places where it, according to me, still makes sense to use "Title Case", for example "ThinLinc Web Access".
Comment 2 Samuel Mannehed cendio 2024-11-04 10:30:10 CET
As part of bug 5114 we've started approaching a decision regarding this bug. The general rule we've been using is sentence case for everything except for a very short list of 4 items:

* ThinLinc
* Web Access
* Web Administration
* Administrator's Guide

For example, that means we should say:

* ThinLinc desktop customizer
* ThinLinc web integration
* ThinLinc profile chooser
* ThinLinc master
* ThinLinc setup
* end-user license agreement
* high availability
... etc.

Note You need to log in before you can comment on or make changes to this bug.