Style/Miscellaneous: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(added playlists guideline, linked to WhatNotToLinkTo (Imported from MoinMoin))
(Long live quality data like "—" and "…" ! (Imported from MoinMoin))
Line 29: Line 29:


What about dashes vs. hyphens? See [http://musicbrainz.org/show/edit/?editid=5281475 http://musicbrainz.org/show/edit/?editid=5281475], I've encountered a similar problem there. Wouldn't it make a lot of sense if we would make full use of Unicode in the database and have some automated heuristic in the tagger to convert to ASCII if necessary? This heuristic could be made optional and dropped when a sufficient number of clients supports Unicode. I mean, the tagger does support Unicode in tags already, and so do several software players. Why should some hardware players pose a restriction for the whole system? Considering European languages, the replacement list shouldn't become too large to handle. Also, it doesn't have to be perfect, because in ASCII you can only do approximations of the correct typography, anyway. I'd volunteer to set up and maintain the list. [[Answer Me|AnswerMe]], please, at least concerning the dashes vs. hyphens question ... Thanks. Editor:selig
What about dashes vs. hyphens? See [http://musicbrainz.org/show/edit/?editid=5281475 http://musicbrainz.org/show/edit/?editid=5281475], I've encountered a similar problem there. Wouldn't it make a lot of sense if we would make full use of Unicode in the database and have some automated heuristic in the tagger to convert to ASCII if necessary? This heuristic could be made optional and dropped when a sufficient number of clients supports Unicode. I mean, the tagger does support Unicode in tags already, and so do several software players. Why should some hardware players pose a restriction for the whole system? Considering European languages, the replacement list shouldn't become too large to handle. Also, it doesn't have to be perfect, because in ASCII you can only do approximations of the correct typography, anyway. I'd volunteer to set up and maintain the list. [[Answer Me|AnswerMe]], please, at least concerning the dashes vs. hyphens question ... Thanks. Editor:selig
<ul><li style="list-style-type:none">It would be probably better to ask on the [[Users Mailing List|mailing list]]. --[[User:LukasLalinsky|LukasLalinsky]]
<ul><li style="list-style-type:none">It would be probably better to ask on the [[Users Mailing List|mailing list]]. --[[User:LukasLalinsky|LukasLalinsky]] I agree with Editor:selig. We ought to have the data in [[MusicBrainz]] rise above the particular limitations of this player or that filesystem of today, because if we don't, then tomorrow when the limitation is removed, our data will still be hobbled. It's the job of the tagger to dumb down the data to the limitations of the destination player or format of the moment. And by the way, this means I disagree with the guideline about "…"; our data ought to favour the ellipsis over three periods "...". — [[User:JimDeLaHunt|JimDeLaHunt]] 2008-01-07
</ul>
</ul>



Revision as of 04:33, 8 January 2008

Miscellaneous Guidelines

This page is for small guidelines that don't need their own wiki page.

Compatability Guidelines

These guidelines exist to minimise unnecessary compatability problems with clients that don't fully support Unicode.

Use of Quotation Marks (" and ')

  • Use standard ASCII single and double quotes " and ' rather than the enhanced versions.
  • Use " (one double quote) for inch.
  • Use ' (one single quote) for feet.

Use of Ellipsis Mark (...)

  • Use "..." (3 full stops) for an ellipsis rather than the special ellipsis character "…".
    • This was discussed on the mailing list here.

"Top something" Playlists

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 WhatNotToLinkTo, it is no OfficialStyleGuideline though but just information that should help editing.

Discussion

What about dashes vs. hyphens? See http://musicbrainz.org/show/edit/?editid=5281475, I've encountered a similar problem there. Wouldn't it make a lot of sense if we would make full use of Unicode in the database and have some automated heuristic in the tagger to convert to ASCII if necessary? This heuristic could be made optional and dropped when a sufficient number of clients supports Unicode. I mean, the tagger does support Unicode in tags already, and so do several software players. Why should some hardware players pose a restriction for the whole system? Considering European languages, the replacement list shouldn't become too large to handle. Also, it doesn't have to be perfect, because in ASCII you can only do approximations of the correct typography, anyway. I'd volunteer to set up and maintain the list. AnswerMe, please, at least concerning the dashes vs. hyphens question ... Thanks. Editor:selig

  • It would be probably better to ask on the mailing list. --LukasLalinsky I agree with Editor:selig. We ought to have the data in MusicBrainz rise above the particular limitations of this player or that filesystem of today, because if we don't, then tomorrow when the limitation is removed, our data will still be hobbled. It's the job of the tagger to dumb down the data to the limitations of the destination player or format of the moment. And by the way, this means I disagree with the guideline about "…"; our data ought to favour the ellipsis over three periods "...". — JimDeLaHunt 2008-01-07