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

Getting all caps #1190

Closed
simonlindgren opened this issue May 21, 2019 · 14 comments
Closed

Getting all caps #1190

simonlindgren opened this issue May 21, 2019 · 14 comments
Labels

Comments

@simonlindgren
Copy link

I am using BBT (5.1.83) in Zotero (5.0.66) with zotpick-pandoc.applescript. My citation key format in BBT is "[auth:lower][year]". But, still, zotpick outputs my references in uppercase, as in [NAME2013B]. Has something gone bad with recent Zotero updates, or am I doing something wrong?

@retorquere
Copy link
Owner

Please verify all of the below before submitting:

  1. you have picked the right category for the issue in the previous screen.
  2. in the Zotero addons screen you can see that you have the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero installed
  3. you are posting a single bug or feature request
  4. you have included a descriptive subject of the problem
  5. you are available for follow-up questions and testing
  6. you have included an error-report ID here generated by reproducing the problem, selecting the problematic reference(s), right-clicking, and submitting an BBT error report from that popup menu

Picking the right issue category is really important. Each category (Export, General error, Import, Key generation, Question) has different instructions for gathering the data necessary required to resolve the issue you are experiencing

The error report is important; it gives me your current BBT settings and a copy of the problematic reference as a test case so I can best replicate your problem. Without it, I'm effectively blind.

@retorquere
Copy link
Owner

If you click http://localhost:23119/better-bibtex/cayw?format=pandoc and pick that reference, what do you see in your browser?

@simonlindgren
Copy link
Author

If I do the localhost:23119 thing, I get the right (lowercase) version of the reference. But if I use the zotpick applescript from https://github.com/davepwsmith/zotpick-applescript to insert in any editor, it gets capitalised.

@retorquere
Copy link
Owner

BBTs activity ends with what ends up in your browser. Where do you see the uppercased version?

@simonlindgren
Copy link
Author

Well, that would then be after BBTs activity ends, as the uppercased version is what comes out if I use the zotpick applescript from https://github.com/davepwsmith/zotpick-applescript to insert in any editor.

@retorquere
Copy link
Owner

retorquere commented May 21, 2019

@simonlindgren
Copy link
Author

I see. It is very odd, as this used to work perfectly before, but not any more.

I have tried inserting in several different editors, so it is not about that either.

Super annoying!

@retorquere
Copy link
Owner

When I run this in Script Editor, I get it pasted into Script Editor without the capitalization. There must be something running on your system that interferes.

@simonlindgren
Copy link
Author

simonlindgren commented May 21, 2019

I've got it! When setting up a new mac (being Swedish as I am) there is the option to set either "Swedish" or "Swedish - Pro" as your input source. I never really understood the difference, so sometimes when setting up a new system I choose one, and sometimes the other. I turns out that it was the "Pro" setting which caused this. Using basic "Swedish" as input source solved it!

@retorquere
Copy link
Owner

Professional Swedes shout all the time?

@simonlindgren
Copy link
Author

Seems like it :)

@retorquere
Copy link
Owner

The B at the end is a dead giveaway BTW. That's the disambiguation postfix and BBT never under any circumstance capitalizes that -- you can't make it if you wanted to.

@simonlindgren
Copy link
Author

Realized now, that it wasn't the Swedish/Swedish Pro thing. The error went away after switching the input source. When switching back to Pro it still works.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants