hmcmathematics / codee-class

LaTeX document class for typesetting submissions to the CODEE Journal.
LaTeX Project Public License v1.3c
1 stars 1 forks source link

Update CODEE style file #1

Closed cmconnelly closed 8 years ago

cmconnelly commented 8 years ago

Would you be interested in helping me update the CODEE style file? We are migrating all of the content from the CODEE web site--I think I mentioned that to you a while back but it's taken a while to get to this point.

The style file is fine except that (1) you have to own MinionPro to produce final documents, which puts the burden on me to do it, and (2) the footer needs to be simplified to remove the document-specific link. (There will be a cover page dynamically generated for each document that will have a document-specific link in it.)

(1) We've decided to go with fouriernc.

http://www.tug.dk/FontCatalogue/urwschoolbookl/

I've attached a version of an older published item with this new font.

\RequirePackage{fouriernc} \RequirePackage[T1]{fontenc}

(2) The footer should be simplified to

CODEE Journal * Article * June 2009 CODEE Journal * Project * June 2009

We don't need the URL anymore. I'm thinking maybe the footer alternates sides? If you think the URL is still nice, we could just link to http://www.codee.org

Also, the san-serif font doesn't seem to be using cmtty in the footer. I don't know why it is different than in the references, for example.

If you don't have time, no worries! But, I thought this might be the kind of project that you'd enjoy.

cmconnelly commented 8 years ago
DY> Would you be interested in helping me update the CODEE
DY> style file?

Definitely! I'm trying to figure out where the class lives -- I have a Subversion repo, but I don't see all the files (e.g., template.tex, sample.tex) that I see in another directory.

Hmm. And I see that the contents of the how-to-prepare-manuscripts.zip has some different files -- the codee.cls file there is the same as the one at the tip of the Subversion repo (so that's good...).

Once I find all the pieces, I'll put it up on Github. I'll start with a private repo, but if you're okay with doing so, I'll move it to a public repo once we've got things sorted out.

It looks like the license is CC Attribution-Noncommercial-Share Alike -- do you want to stick with that, or move to the LaTeX Project Public License? (Or something else?)

DY> We are migrating all of the content from the CODEE web
DY> site--I think I mentioned that to you a while back but
DY> it's taken a while to get to this point.

Yes; glad that it's underway.

DY> The style file is fine except that (1) you have to own
DY> MinionPro to produce final documents, which puts the
DY> burden on me to do it,

Yup.

DY> and (2) the footer needs to be simplified to remove the
DY> document-specific link. (There will be a cover page
DY> dynamically generated for each document that will have a
DY> document-specific link in it.)

Generated by the CCDL system? (I.e., we don't have to do anything special to an article to get it to work?)

DY> (1) We've decided to go with fouriernc.

DY> http://www.tug.dk/FontCatalogue/urwschoolbookl/

DY> I've attached a version of an older published item with
DY> this new font.

DY> \RequirePackage{fouriernc} \RequirePackage[T1]{fontenc}

Okay, I'll take a look. URW Schoolbook (or TeX Gyre Schola) is wider than Minion/Times, so using it will change line breaks, and, possibly, page breaks.

Have you looked at the fonts we're using the in the current version of the thesis/Clinic classes? We switched to New PX (newpxtext) for text (http://www.tug.dk/FontCatalogue/newpx/), Inconsolata (inconsolata) for typewriter text (http://www.tug.dk/FontCatalogue/inconsolata/), and Source Sans Pro (sourcesanspro) for sans-serif (http://www.tug.dk/FontCatalogue/sourcesanspro/). (We would be using Source Code Pro instead of Inconsolata, but they decided to put in ligatures, and the existing TeX package/generated fonts use the ligatures, which looks terrible and is completely wrong. I have a modified version of the fonts, but that doesn't fix the issue for anyone else.)

DY> (2) The footer should be simplified to

DY> *CODEE Journal * *Article * June 2009 *CODEE Journal *
DY> *Project * June 2009

Okay, easy.

DY> We don't need the URL anymore.  I'm thinking maybe the
DY> footer alternates sides?  If you think the URL is still
DY> nice, we could just link to http://www.codee.org

If that URL will live on, then linking to it can't hurt. But I'll look and see....

DY> Also, the san-serif font doesn't seem to be using cmtty in
DY> the footer.  I don't know why it is different than in the
DY> references, for example.

I'll look....

DY> If you don't have time, no worries!  But, I thought this
DY> might be the kind of project that you'd enjoy.

Yes! So much more fun than everything else I should be doing! :)

I'll invite you to the repo as soon as I have it up.

cmconnelly commented 8 years ago

Sounds perfect, Claire. The "how-to-prepare-manuscripts.zip" has the most recent files as far as I know. That would be great if you put it on Github. We can share it publicly from there once we're ready to go live with it.

If you don't mind, can we try two different versions? One with the font I suggested and one with the fonts you suggested. Then I can get the other editorial board members to give their thoughts.

Thanks! Darryl

cmconnelly commented 8 years ago

Licensing question split out into #2.

cmconnelly commented 8 years ago

Font question split out into #3.

cmconnelly commented 8 years ago

Footer question split out into #4.