[mb-users] Correct typography

[Philip Jägenstedt]

I share the fears of one poster that this would drag us into endless
debates on style for which there can be no correct solution. Adding to
the pain is that different languages use different quotes (e.g.
Swedish uses two right-quotes if I'm not mistaken) and what to do when
the stuff inside the quotes is in one language and the words preceding
it are in another lanuage? I'm in pain just thinking about it.

That I can't grasp the issues at hand doesn't mean that this is a bad
idea though...

Philip

On 9/15/07, Chris B <chris at whenironsattack.com> wrote:
> let us also remember that 'correct' does not necessarily mean that it's
> 'best'. i would put money that next to no real release track listings use
> the proper ellipsis character. what benefit is using the real one?
> + 'correct'
> - not easily entered by users
> - not easily tagged
> - different to real releases
>
> personally i don't mind, but at the very least there needs to be the
> surrounding work done to a) convert existing entries, b) automatically fix
> new entries, and c) tag with the data correctly, as the benefits to this
> aren't obvious.
>
>
>  On 13/09/2007, Philipp Wolfer <phw at rubyforge.org> wrote:
> > 2007/9/13, Mika Heiska <kilualmighty at gmail.com>:
> > > Philipp Wolfer wrote:
> > > > MusicBrainz is more than just the tagger.
> > >
> > > This seems to be always the stock reply when these kind of questions
> > > arise. I mean, sure, I know MBz isn't just the tagger, but it's a big
> > > part of it. However, during the 3 years I have been around, tagger has
> > > always gotten the shorter straw. There never seem to be compromises,
> > > tagger always gets shafted in favour of whatever brandspanking new
> > > feature someone comes up with that helps the database in whatever way. I
> > > can't actually point any specific examples (haha, this mail just lost a
> > > little weight) but we all know it's true.
> >
> > The point I wanted to make here is that the tagger should not be the
> > limiting factor for the use of special typographic characters. In many
> > cases, including the web, the use of the correct typography can make a
> > track listing more pleasant to read (ellipsis is maybe debatable
> > here).
> >
> > And as some said before it is much easier to convert a special
> > character into a more general form than vice versa. So IMHO the best
> > solution would be to not limit the characters on server side and let
> > the tagger application offer an option to convert the characters. Of
> > course this needs to be implemented, but this could be easily done in
> > the next version of Picard.
> >
> > I agree, however, that those characters should not be widely used
> > until this is properly supported in the tagger. But in track titles
> > that already use Unicode (e.g. Japanese) I see no problem in using
> > them.
> >
> > --
> > Philipp Wolfer
> >
> > _______________________________________________
> > MusicBrainz-users mailing list
> > MusicBrainz-users at lists.musicbrainz.org
> >
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users
> >
>
>
> _______________________________________________
> MusicBrainz-users mailing list
> MusicBrainz-users at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users
>