Closed HughP closed 4 months ago
All that condenses down to "U+01C2
should be exported as \textdoublebarpipe
" right?
Yep!
All the best, -Hugh
Sent from my iPhone
On Mon, Jun 3, 2024 at 3:20 PM Emiliano Heyns @.***> wrote:
All that condenses down to "U+01C2 should be exported as \textdoublebarpipe" right?
— Reply to this email directly, view it on GitHub https://github.com/retorquere/zotero-better-bibtex/issues/2896#issuecomment-2146224407, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAJ2JRQV45NU2SZ3ZFNXRLZFTT3ZAVCNFSM6AAAAABIXEIYMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGIZDINBQG4 . You are receiving this because you authored the thread.Message ID: @.***>
When I export a bibliographic reference containing Unicode character
“ǂ” (U+01C2)
it is exported as\textdoublepipe
Unicode U+01C1
. As I understand things, in text mode, it should be exported as\textdoublebarpipe
That is correct, but it will only work with tipa
loaded.
else a user message should be given that the character is not exportable (+plus the reason).
That is not possible. Zotero doesn't allow exporters to provide feedback to the user other than "success" or "failed".
Text mode seems to be the default for BBT
This is not precisely correct. The default for Better BibTeX is text mode (but it can be changed). The default for Better BibLaTeX is unicode.
or if it expected that users will need to add
\usepackage{tipa}
to their preamble.
The symbol was missing from the table, I've added it now; a build will drop here in a bit with that baked in.
In BBT, you can specify what packages you have loaded. I'll add missing packages to the quality report later, but you can see what characters need special packages and which packages provides them here.
Zotero RDF of record (for ingest and local testing)
Appreciated, but next time please send a debug log by right-clicking the entry and select "Send BBT Debug log" from the popup menu (the ID will have -refs
in it). That sends me the entry in a way that my test suite can pick it up automatically, builds a named testcase from it, etc.
:robot: this is your friendly neighborhood build bot announcing test build 6.7.203.2896.6361 ("update unicode mapping")
This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.203.2896.6361, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
Can you test build 6361?
Not resolved.
I downloaded and installed the test build provided by the bot, and I still get \textdoublepipe
. I've rebooted Zotero twice. And tried again with the export. same result. here are the link logs.
YR3BXCQP-euc/6.7.203.2896.6361-6 DPF9RCHH-refs-euc/6.7.203.2896.6361-6
~Have you configured BBT to load the tipa
package support as per those links above?~ you need to follow the instructions from here (also read the top of the page).
Thank you for highlighting those extra steps. I missed them (in the zotero settings). I can confirm that post adding tipa
to the appropriate setting that the export is now working.
FYI there is a link not rendering on the documentation page at: https://retorque.re/zotero-better-bibtex/installation/preferences/hidden-preferences/index.html#packages
I do wonder though why the software inserts a \textdoublepipe
for this character at all (when there is no tipa
set in the settings). I mean, the two Unicode characters aren't interchangeable. It seems to be a case of see " A" return "B" when the user would be expecting an error or return "null" or return "A".
Thanks for the feedback! Just so you know, GitHub doesn't let me control who can close issues, and @retorquere likes to leave bug reports and enhancements open as a nudge to merge them into the next release.
Again, I can only have the export succeed or fail without further comment, and the latter, without any indication what went wrong, is entirely useless to the user. I'm going to add it to the quality report, which will be much more informative. I might also add an option to just blindly assume all required packages are available, which is the behavior you want.
The user must also be in control of what packages are assumed. Not all packages are available everywhere, and not all packages are compatible with each other.
It's already in the quality report
Debug log ID
Q4B9RHJW-euc/6.7.203-6
What happened?
When I export a bibliographic reference containing Unicode character
“ǂ” (U+01C2)
(info) it is exported as\textdoublepipe
Unicode U+01C1
. As I understand things, in text mode, it should be exported as\textdoublebarpipe
else a user message should be given that the character is not exportable (+plus the reason). The example below shows that the described behavior occurs in the title and the abstract. The limits of my knowledge are tested with regards to the LaTeX text mode. That is, I usually use XeLaTeX and UTF-8 encoding (which is also my default encoding within Zotero), but for my current project I need to use pdfLaTeX and text mode. Text mode seems to be the default for BBT and also works with XeLaTeX just fine. The challenging thing as a user is when BBT appears to export without issue and the wrong character is exported. Because I am not familiar with LaTeX text mode, I am not sure if\textdoublebarpipe
is present in the default document set up or if it expected that users will need to add\usepackage{tipa}
to their preamble. I do add this package and when do and also I change the\textdoublepipe
to\textdoublebarpipe
things render correctly. The issue is that I shouldn't have to edit the bibTeX entry after export. Ether the original character“ǂ” (U+01C2)
should be exported or\textdoublebarpipe
should be used.\textdoublepipe
is unacceptable because it is not the same visually or even the same character.I found the linked LaTeX symbols reference list helpful.
Versions: Zotero 6.0.35, BBT 6.7.203 My rendering results are tested using the Overleaf platform.
Example BBT output
Zotero RDF of record (for ingest and local testing)