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

Primer, sec. "cs:info Element" and sec. "cs:bibliography Element" are not valid CSL #150

Open
lucabalsanelli opened this issue Apr 5, 2022 · 6 comments

Comments

@lucabalsanelli
Copy link
Contributor

Primer, sec. "cs:info Element" and sec. "cs:bibliography Element" are not valid CSL according to https://validator.citationstyles.org/, for 2 errors.

  1. This
<info>
  <--! omissis -->
  <category citation-format="author-date"/>
  <category field="science">
  <--! omissis -->
</info>

should be (issue: end tag)

<info>
  <--! omissis -->
  <category citation-format="author-date"/>
  <category field="science"/>
  <--! omissis -->
</info>
  1. and this
<bibliography>
  <!-- omissis -->
  <layout suffix="." delimiter=", ">
    <group delimiter=". ">
      <!-- omissis -->
    </group>
    <group>
      <!-- omissis -->
    </group>
    <text variable="page"/>
  </layout>
</bibliography>

should be (issue delimiter attribute in cs:layout element)

<bibliography>
  <!-- omissis -->
  <layout suffix=".">
    <group delimiter=", ">
      <group delimiter=". ">
        <!-- omissis -->
      </group>
      <group>
        <!-- omissis -->
      </group>
      <text variable="page"/>
    </group>
  </layout>
</bibliography>

I wanted to edit in place but I didn't know which branch since it's not possible on master.

@bwiernik
Copy link
Member

bwiernik commented Apr 5, 2022

Thanks! Can you open a pull request against master? I can take care of any other branches

@lucabalsanelli lucabalsanelli changed the title Primer, sec. "cs:bibliography Element" is not valid CSL Primer, sec. "cs:info Element" and sec. "cs:bibliography Element" are not valid CSL Apr 6, 2022
lucabalsanelli added a commit to lucabalsanelli/documentation that referenced this issue Apr 6, 2022
lucabalsanelli added a commit to lucabalsanelli/documentation that referenced this issue Apr 6, 2022
@lucabalsanelli
Copy link
Contributor Author

Did it. I don't understand if it's me that can/should merge this pull request. I never exactly got the handle of pull requests on GitHub.

@bwiernik
Copy link
Member

bwiernik commented Apr 6, 2022

I don't see any pull request in the CSL repo. Maybe you accidentally opened it on your fork? Can you give me a link to what you are seeing?

@denismaier
Copy link
Member

denismaier commented Apr 6, 2022

The pull request was against @lucabalsanelli's fork, see here.

@lucabalsanelli You need to open the pull request against the master branch in this repo. Here's how: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

@lucabalsanelli
Copy link
Contributor Author

Thanks for the "accidentally", but I in fact never grabbed the social features of github... I'm going to read the documentation, so hopefully I'm going to switch from being a git user to a git+hub user.

@lucabalsanelli
Copy link
Contributor Author

did my best to read the github manual

bwiernik added a commit that referenced this issue Apr 19, 2022
csl-validity restored as per issue #150
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants