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

Taylor & Francis Reference Style needs updating #556

Open
ehsanx opened this issue Dec 26, 2023 · 5 comments · May be fixed by #557
Open

Taylor & Francis Reference Style needs updating #556

ehsanx opened this issue Dec 26, 2023 · 5 comments · May be fixed by #557
Labels
feature a feature request or enhancement help wanted ❤️ we'd love your help!

Comments

@ehsanx
Copy link

ehsanx commented Dec 26, 2023

Taylor & Francis Reference Style is different from the one provided by rticles::tf_article

The current rticles::tf_article provides the following in the tex file:
\usepackage{natbib}% Citation support using natbib.sty
\bibpunct[, ]{(}{)}{;}{a}{}{,}% Citation support using natbib.sty

However, as per https://files.taylorandfrancis.com/tf_S.pdf it should be simply
\usepackage[numbers]{natbib}


R version 4.3.0 (2023-04-21 ucrt)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 11 x64 (build 22621), RStudio 2023.12.0.369

Locale:
LC_COLLATE=English_Canada.utf8 LC_CTYPE=English_Canada.utf8 LC_MONETARY=English_Canada.utf8
LC_NUMERIC=C LC_TIME=English_Canada.utf8

time zone: America/Vancouver
tzcode source: internal

Package version:
base64enc_0.1.3 bslib_0.5.1 cachem_1.0.8 cli_3.6.1 digest_0.6.31
ellipsis_0.3.2 evaluate_0.23 fastmap_1.1.1 fontawesome_0.5.2 fs_1.6.3
glue_1.6.2 graphics_4.3.0 grDevices_4.3.0 highr_0.10 htmltools_0.5.5
jquerylib_0.1.4 jsonlite_1.8.7 knitr_1.45 lifecycle_1.0.4 magrittr_2.0.3
memoise_2.0.1 methods_4.3.0 mime_0.12 R6_2.5.1 rappdirs_0.3.3
rlang_1.1.1 rmarkdown_2.25 rticles_0.25 sass_0.4.7 stats_4.3.0
stringi_1.7.12 stringr_1.5.0 tinytex_0.48 tools_4.3.0 utils_4.3.0
vctrs_0.6.4 xfun_0.39 yaml_2.3.7

By filing an issue to this repo, I promise that

  • [ x] I have fully read the issue guide at https://yihui.name/issue/.
  • [ x] I have provided the necessary information about my issue.
    • If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.
    • If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included xfun::session_info('rticles'). I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version: remotes::install_github('rstudio/rticles').
    • If I have posted the same issue elsewhere, I have also mentioned it in this issue.
  • [ x] I have learned the Github Markdown syntax, and formatted my issue correctly.

I understand that my issue may be closed if I don't fulfill my promises.

@cderv
Copy link
Collaborator

cderv commented Dec 27, 2023

Thanks for opening an issue.

It seems indeed there was an update in the templates we can find at : https://files.taylorandfrancis.com/InteractCADLaTeX.zip

% interactcadsample.tex
% v1.04 - May 2023

\documentclass[]{interact}

\usepackage{epstopdf}% To incorporate .eps illustrations using PDFLaTeX, etc.
\usepackage{subfigure}% Support for small, `sub' figures and tables
%\usepackage[nolists,tablesfirst]{endfloat}% To `separate' figures and tables from text if required

\usepackage{natbib}% Citation support using natbib.sty
\bibpunct[, ]{(}{)}{;}{a}{}{,}% Citation support using natbib.sty
\renewcommand\bibfont{\fontsize{10}{12}\selectfont}% Bibliography support using natbib.sty

But the bibpunct line is still there.

I can do the update for the template, but still this line would be there.

For which journal https://files.taylorandfrancis.com/tf_S.pdf ? maybe they use another template ?

It seems this Zip template uses the Chicago style author date (https://files.taylorandfrancis.com/tf_ChicagoAD.pdf)

@cderv cderv added feature a feature request or enhancement help wanted ❤️ we'd love your help! labels Dec 27, 2023
cderv added a commit that referenced this issue Dec 27, 2023
@cderv
Copy link
Collaborator

cderv commented Dec 27, 2023

I have updated to latest file from bundle linked.

Please do share any other T&F template that may not be compatible with this one.

It was initially added in #218 by @dleutnant and may not cover all the possible Journals

@ehsanx
Copy link
Author

ehsanx commented Dec 31, 2023

For which journal https://files.taylorandfrancis.com/tf_S.pdf ? maybe they use another template ?

I received it from the "Journal of Applied Statistics". Thanks!

@cderv
Copy link
Collaborator

cderv commented Jan 3, 2024

So this one: https://www.tandfonline.com/journals/cjas20

From their instruction (https://www.tandfonline.com/action/authorSubmission?show=instructions&journalCode=cjas20) they have other template available at https://files.taylorandfrancis.com/InteractTFSLaTeX.zip

This templates does have

\usepackage[numbers,sort&compress]{natbib}% Citation support using natbib.sty
\bibpunct[, ]{[}{]}{,}{n}{,}{,}% Citation support using natbib.sty

and probably other differences like

\bibliographystyle{tfs}

This bst file does follow : http://www.tandf.co.uk/journals/authors/style/reference/tf_S.pdf

So probably those options can help... the templates needs to be adapted to pass those and it should be fine 🤔

Not sure we can do one template for all journals - an author would need to download the resources from the website probably and use them with the rticles template.

@cderv cderv linked a pull request Jan 3, 2024 that will close this issue
@cderv
Copy link
Collaborator

cderv commented Jan 3, 2024

Something does not seem to work ok with tfs.bst provided in the template... So it needs more work.

You have the PR linked if you want to try and help adapt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a feature request or enhancement help wanted ❤️ we'd love your help!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants