[uf-discuss] Re: X2C (Was Citation Microformat: Lazyweb...)

[Michael McCracken]

On 10/7/06, Brian Suda <brian.suda at gmail.com> wrote:
> Thanks for all your comments. I have fixed the Author issue, it now
> concatenates them with " and ". I have also changed the "" to {} so
> now i don't have escape quotes. It is all uploaded so you can keep
> testing. (i still need to escape non-ascii characters, but that is not
> really an issue with the microformat)

No, and depending on how the bibtex is being consumed, you may be able
to get away with UTF-8 anyway.

> i'm not sure if we should move technical issues to the dev list and/or
> we should keep the debate about KEYs and other Citation issues on the
> discuss list?

Now that I have a working implementation, I've subscribed to the dev
list. I'll post there about any X2C bug reports & suggestions.

I think the debate about keys, etc belongs on discuss, though - since
I assume most of the participants aren't on -dev.

-mike

> -brian
>
> On 10/6/06, Michael McCracken <michael.mccracken at gmail.com> wrote:
> > ...
> > >
> > > This isn't valid bibtex for three reasons:
> > > It's missing a key, a type, and the double-quotes around "HPC" are a
> > > syntax error.
> > >
> > > In bibtex you can enclose the fields in braces or double-quotes. I
> > > prefer braces, because then you don't need to worry about
> > > latex-escaping double-quotes inside the fields. (And many consumers of
> > > bibtex will still choke on even properly escaped double-quotes).
> > >
> > > For the missing elements, we should decide whether or not it's a
> > > SHOULD (so X2C needs a reasonable default) or a MUST, where I need to
> > > find a way to get that data in there.
> > >
> > > I think key/id and type (not format) are both SHOULDs.
> >
> > Here I forgot to mention what the reasonable defaults for BibTeX should be.
> >
> > In case of a missing type, 'misc' is appropriate. Any contiguous
> > sequence of letters is fine syntatically for a bibtex type, but spaces
> > are bad, for example "@Journal Article{foo, ...}" is invalid.
> >
> > In case of a missing key/uid - using something unique to the page is fine.
> > Doing something unique and meaningful is better, like Author1YearTitle
> > (e.g. "Suda06Microformats"), like this:
> > @misc{suda06Microformats, author = {Suda, Brian}, Title ="Microformats"}
> >
> > -mike
> >
> > --
> > Michael McCracken
> > UCSD CSE PhD Candidate
> > research: http://www.cse.ucsd.edu/~mmccrack/
> > misc: http://michael-mccracken.net/wp/
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss at microformats.org
> > http://microformats.org/mailman/listinfo/microformats-discuss
> >
>
>
> --
> brian suda
> http://suda.co.uk
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>


-- 
Michael McCracken
UCSD CSE PhD Candidate
research: http://www.cse.ucsd.edu/~mmccrack/
misc: http://michael-mccracken.net/wp/