[mb-style] [Clean up CSG] Correct punctuation (was: Typography)
Brian Schweitzer
brian.brianschweitzer at gmail.com
Sat Feb 16 09:46:00 UTC 2008
> I can't outright disagree with any of what you said. Instead, I've
> been pleading that we consider the relative value versus the cost. In
> other words, a little bit of incorrectness might be worth the savings
> in
> hassle for the users.
>
> > No-one (yet) argued we should impose a perfect standard twice the size
> > of what we have now and then out-vote anything that doesn't conform. The
> > proposal was just to define correctness in the (few and rather uncommon)
> > cases where the current rules are "just use ASCII", and replace the rule
> > with "Please do it the nice way if you can and care. Use ASCII if you
> > want to add something, but don't change it if someone does it the nice
> > way". I think that would scare anyone away.
>
> My problem with this approach the end result: A database where the
> rules are not applied uniformly and the data is inconsistent. Worse,
> this
> inconsistency is *explicitly condoned* by the guidelines.
Ok, on typography, I'm willing to drop the idea, for the moment. I
would much rather focus on getting CSG finished and passed, even if it
has to pass with 'plain' typography still required. In a few years,
once we do actually have 'generic work objects', and not just
wikilists, perhaps we can revisit the issue, with a different outcome,
as then perhaps the system will be able to help us make sure correct
punctuation is both easy and consistent.
If I could perhaps, though, suggest a compromise:
* I think we're all thinking Latin script. Would we be able to agree
that, for Latin script, standard punctuation should be used, but
specifically with regards to quotation marks (not dashes, colons,
etc), if the language is written in a non-Latin script,
language-correct quotation marks should be used? This would allow us
to avoid mixing Latin punctuation into Japanese, Chinese, Korean, etc
titles, allowing them to use those square things (whatever they're
called), or whatever else is correct in that language+script. It also
would allow us to avoid any potential conflicts between CSG and
JapaneseArtistsException.
* Further, could we agree that language-correct punctuation spacing
rules (as defined in the proper CapitalizationStandard) should be
followed, so that CSG doesn't come into conflict with, for example,
CapitalizationStandardFrench? (Note, saying nothing here about the
punctuation, *only* spacing around the punctuation.) This is pretty
much what we've been doing anyhow, this just would actually write the
exception into the guideline, so any such CSG - CapsStandard conflict
has a clear order of which should be followed.
Brian
More information about the Musicbrainz-style
mailing list