On Wed, Nov 17, 2010 at 10:25 PM, Alex Mauer <[email protected]> wrote:

> On 11/17/2010 02:06 PM, SwissChris wrote:
> > I think we should add at least a warning that the use of such special
> > punctuation Characters is language specific and should not be changed
> > according to english rules in other languages if one isn't absolutely
> > certain of what he does.
>
> This guideline (in present or future form) makes no recommendations
> about which special character to choose, only a general recommendation
> to prefer the special characters over generic characters, so I think
> this shouldn’t be a problem.  I made the text about dash a little more
> general in order to indicate that other characters may be needed (such
> as the non-breaking hyphen needed in your example).
>

Thanks. Looks good


>
> I also added some cautionary text about making corrections.
>

I like that too

>
> > A link to the language specific
> > CapitalizationStandard guidelines would be helpful too
>
> None of them seem to have much to say about punctuation.  This guideline
> just tells editors that they should use whatever appears on the release.
>

I'm not so sure this is a good idea: We know from the discussions on
Capitalization that grammatical and typographic accuracy is the least of the
concerns of the people making the covers. We should at least add "what
appears on the cover or – better – what is typographically correct in a
specific language"

 Is there something I’m missing?
>

If we no longer prone the use of simple ASCII characters, there will
certainly be the need to add some additional guidelines to the language
specific guides about typographically correct use.

Chris/chabreyflint

>
> —Alex Mauer “hawke”
>
>
> _______________________________________________
> MusicBrainz-style mailing list
> [email protected]
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
>
_______________________________________________
MusicBrainz-style mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style

Reply via email to