Difference between revisions of "User:PBryan/RBC Changes"

From MusicBrainz Wiki
(New page: ==Use of special characters== The use of certain special characters is preferred. Generic characters should be used only where it is clear that they are used on the release (e.g. typewri...)
 
(Proposed changes.)
 
Line 1: Line 1:
==Use of special characters==
+
==Use of Unicode characters==
  
The use of certain special characters is preferred.  Generic characters should be used only where it is clear that they are used on the release (e.g. typewritten track listings). Editors should replace generic characters with their more specific equivalents.
+
Specific (Unicode) characters are preferred over their generic typewritten (ASCII) equivalents. Editors should replace generic characters with more specific equivalents.  
  
While there are several ways to enter these characters including various key combinations as well as copy and paste, you may find that it’s all too much hassle. In this case, feel free to use the generic equivalents.  Other editors can edit to the preferred characters.  However, be careful when making corrections, as the usage rules vary for different languages.
+
While there are several ways to enter Unicode characters—including various key combinations and copy/paste—it may be difficult in your configuration. In such case, use generic typewritten equivalents.  Other editors can later edit with preferred characters.
  
;Apostrophe: A true apostrophe (’) is preferred in place of a typewriter apostrophe (').  Use ' only if it is clearly as it appears on the release, or if you can’t easily enter the preferred character.
+
; Apostrophes: A true apostrophe (’) is preferred over the typewritten apostrophe (').
;Quotation marks: Use the mark that appears on the release.  Use " only if it is clearly as it appears on the release, or if you can’t easily enter the preferred characters.  Other common variations include:
+
; Quotation marks: Use the type of mark that appears on the release:
:; single quotes: ‘ and ’
+
:; single quotation marks: ‘ and ’ are preferred over the typewritten apostrophe ('),
:; guillemets: « »  and ‹ › (note difference from  < and >)
+
:; double quotation marks: “ and ” are preferred over the typewritten quotation mark ("),
:; low quotes: „ and ‚ (note difference from comma: ,)
+
:; guillemets: double « »  and single ‹ › are preferred over the typewritten < and >,
;Primes: Use single prime (′), double-prime (″), and triple-prime (‴) where appropriate. Single prime indicates minutes and feet; double-prime indicates seconds and inches. Triple-prime is rarely used.
+
:; low quotes: „ and ‚ are preferred over the typewritten comma (,).
;Ellipsis: Use the ellipsis character (…) instead of three periods (...), unless you cannot easily enter the preferred character.
+
;Primes: Use single prime (′), double-prime (″), and triple-prime (‴) where appropriate. Single prime indicates minutes and feet; double-prime indicates seconds and inches. Triple-prime is rarely used.
;Dashes, hyphens, and minus signs: Use the appropriate hyphen (‐), minus sign (−), em dash (), en dash (), or other dash as it appears on the release.  If you can’t easily enter these characters, or can’t determine which is correct, use - (hyphen-minus) for en dash, hyphen, and minus; and -- for em dash and quotation dash.  Other editors should correct these where possible, unless it is clear that the release actually uses typewriter-dash(es).
+
;Ellipsis: Use the ellipsis character (…) is preferred over three typewritten periods (...).
 
+
;Hyphen: The typewritten hyphen character (-) should be used for all hyphenation.
=="Top something" Playlists==
+
;Dashes and minus signs: Use of the minus sign (−), en dash (), em dash () are preferred over the use of the typewritten hyphen (-). The use of typewritten dashes should be retained if a release uses such characters.
 
 
Bootleg torrents that are compilations based on playlists of charts authorities (like Billboard's) should not be stored in MusicBrainz as releases. These playlists are often copyrighted by their issuers.
 
 
 
==Other Do-Not's==
 
 
 
There's some guiding information available [[What Not To Link To]].  It is not an [[Official Style Guideline]], but is information that should help while editing.
 

Latest revision as of 17:44, 18 November 2010

Use of Unicode characters

Specific (Unicode) characters are preferred over their generic typewritten (ASCII) equivalents. Editors should replace generic characters with more specific equivalents.

While there are several ways to enter Unicode characters—including various key combinations and copy/paste—it may be difficult in your configuration. In such case, use generic typewritten equivalents. Other editors can later edit with preferred characters.

Apostrophes
A true apostrophe (’) is preferred over the typewritten apostrophe (').
Quotation marks
Use the type of mark that appears on the release:
single quotation marks
‘ and ’ are preferred over the typewritten apostrophe ('),
double quotation marks
“ and ” are preferred over the typewritten quotation mark ("),
guillemets
double « » and single ‹ › are preferred over the typewritten < and >,
low quotes
„ and ‚ are preferred over the typewritten comma (,).
Primes
Use single prime (′), double-prime (″), and triple-prime (‴) where appropriate. Single prime indicates minutes and feet; double-prime indicates seconds and inches. Triple-prime is rarely used.
Ellipsis
Use the ellipsis character (…) is preferred over three typewritten periods (...).
Hyphen
The typewritten hyphen character (-) should be used for all hyphenation.
Dashes and minus signs
Use of the minus sign (−), en dash (–), em dash (—) are preferred over the use of the typewritten hyphen (-). The use of typewritten dashes should be retained if a release uses such characters.