Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template for the IEEE Transaction Journals #97

Merged
merged 5 commits into from
Jun 8, 2017
Merged

Conversation

Emaasit
Copy link
Contributor

@Emaasit Emaasit commented Dec 1, 2016

Latex template can be found on the conference site at http://www.ieee.org/conferences_events/conferences/publishing/templates.html

$endif$
% Pandoc header
$for(header-includes)$
$header-includes$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are including header-includes twice.

\printbibliography$if(biblio-title)$[title=$biblio-title$]$endif$

$endif$
$for(include-after)$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't see the matching include-before




% Some very useful LaTeX packages include:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As things stand now there really isn't a way for users to activate any of these classes. You could make these options at the format function level and then pass pandoc arguments along to conditionally enable them.

@jjallaire
Copy link
Member

Could you also add a call to test the format here: https://github.com/rstudio/rticles/blob/master/tests/testthat/test_formats.R#L42-L48

@coatless
Copy link
Contributor

Would it be okay if I contribute or submit the requested revisions to this PR? I would like to get the IEEEtrans format available in rticles.

@Emaasit
Copy link
Contributor Author

Emaasit commented Jan 18, 2017

@coatless Yes, please. Go ahead. Due to work overload here at school, I had planned to do the revisions at the end of this month.

@coatless
Copy link
Contributor

@Emaasit: Could you give me write access to your fork? Or would you prefer if I PR'd against your fork and on merge those changes would appear here?

@Emaasit
Copy link
Contributor Author

Emaasit commented Jan 18, 2017

@coatless I have added you as a collaborator to my fork. That gives read/write permissions.

@coatless
Copy link
Contributor

Addressed the concerns in 136c182.

As a side note, @Emaasit, did you want to add in support for the journal, technote, peerreview, and peerreviewca paper modes? Or just keep it focused on the conference mode?

@Emaasit
Copy link
Contributor Author

Emaasit commented Jan 21, 2017

@coatless Thanks for those patches. Two more fixes are needed before it's perfect.

  • The sections should be numbered: How about we just add number_sections: true in the yaml header

  • The References should be numbered

Regarding support for other articles formats, I think we should add only the journal format for now.

@coatless
Copy link
Contributor

Good catches by the way.

  1. Why not remove this variable entirely as IEEE requires section to be numbered?
  2. Regarding citations:
  • The IEEE style will not work with biblatex since the package is anti .bst. However, it seems as if using \usepackage[style=ieee]{biblatex} to get around this hiccup is not possible either. I'll test this out on a different machine tomorrow. An alternative solution to address this issue is to just fall back and use the bibtex backend.

  • Meanwhile, the natbib setup can easily be handled by:

\usepackage[numbers]{natbib}
\bibliographystyle{IEEEtranN}

where IEEEtranN is the IEEEtranN.bst from IEEEtran.

Regarding supporting the journal in addition to conference mode, I'll add a few variables in that allow a paper mode to be specified. The main task to supporting different modes is being able to handle the different styles of author listings and allowing for IEEE keywords.

@espinielli
Copy link
Contributor

espinielli commented Jun 8, 2017

This PR looks quite a mature contribution...is there any plans to merge it?
(The merge conflict is trivial to solve...I did it in my own cloned repo)

@jjallaire jjallaire merged commit f54e466 into rstudio:master Jun 8, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants