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.

Sign up for GitHub

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

Jump to bottom

Report entries with the bibtex 'number' field are translated to 'issue' variable #295

Open
cgevans opened this issue Mar 17, 2025 · 3 comments · May be fixed by #296
Open

Report entries with the bibtex 'number' field are translated to 'issue' variable #295

cgevans opened this issue Mar 17, 2025 · 3 comments · May be fixed by #296

Comments

@cgevans
Copy link

cgevans commented Mar 17, 2025 •
edited
Loading

Bibtex/biblatex has a number field, which may or may not be numeric. Hayagriva translates both number and issue to issue. CSL also has a number field, giving the example of a report number; while this is a number variable, the CSL spec appears to allow the variable to be non-numeric content.

In my case, I had been trying to handle this technical report:

@techreport{winfree_simulations_1998,
  title = {Simulations of Computing by Self-Assembly},
  author = {Winfree, Erik},
  year = {1998},
  number = {CSTR1998.22},
  institution = {Caltech}
}

Here, it seems like number should be translated to serial-number in Hayagriva's format, and in turn into number in CSL, rather than issue. Additionally, 'type' likely needs to be translated to 'genre'.

As an example of this problem, the CSL for 'american-chemical-society' includes the following for a report:

            <choose>
              <if type="report">
                <group delimiter=" ">
                  <text variable="genre"/>
                  <text variable="number"/>
                </group>
              </if>
            </choose>
@cgevans cgevans changed the title Bibtex entries with non-numeric 'number' field, supported by bibtex, are not read/translated properly Bibtex report entries with 'number' field are translated to 'issue' variable. Mar 17, 2025
@cgevans
Copy link
Author

cgevans commented Mar 17, 2025

Apologies - I initially was confused about what the actual bug was here that was preventing my modified CSL style (to include the technical report number) from working, thinking that it was the non-numeric content, rather than number being translated to issue in contexts where number was correct.

@cgevans
Copy link
Author

cgevans commented Mar 17, 2025

I now notice that 'type' in biblatex should likely be translated to 'genre' in CSL for reports, as well.

@cgevans cgevans changed the title Bibtex report entries with 'number' field are translated to 'issue' variable. Report entries with 'number' field are translated to 'issue' variable (from both bibtex and yaml) Mar 17, 2025
@cgevans
Copy link
Author

cgevans commented Mar 17, 2025 •
edited
Loading

Actually, it appears the problem here is that the bibtex number, in this instance, needs to be translated to serial-number in Hayagriva's format, which is then translated to number in CSL.

I'd note that in this instance, Hayagriva's choice of serial-number seems somewhat unexpected and different than everything else (bibtex / biblatex / csl / terminology in style guides / etc), though number is frustratingly vague and generic.

@cgevans cgevans changed the title Report entries with 'number' field are translated to 'issue' variable (from both bibtex and yaml) Report entries with the bibtex 'number' field are translated to 'issue' variable Mar 17, 2025
@cgevans cgevans linked a pull request Mar 17, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

biblatex type to genre, number to serial for non-article. cgevans/hayagriva
1 participant
@cgevans