Not sure how to format xml here but the style id is referenced as:

http://www.zotero.org/styles/bulletin-of-the-seismological-society-of-america

I am using the chrome plugin, and the doi lookup in the app, to add items to the library.

In the app, the doi field looks correct, eg. does not use the escapes.

Well, I cannot change the doi with its odd properties. So I am looking for a way to deal with those. Perhaps manually, eg. search/replace after generation.

https://docs.citationstyles.org/en/stable/specification.html does not seem to provide special formatting of urls. So perhaps Zotero internally provides the doi with escapes to the style ?

Thanks.

Let me revive this post to open a discussion on how Zotero should deal with older DOIs with odd characters such as '[]<>' and others which are somewhat in conflict with the use of DOIs as URLs.

Please note that any changes following from this discussion would not affect newer DOIs.

The typical method to deal with odd characters in URLs is to replace them with a hexadecimal number which begins with a percent '%' sign. This works well in web browsers but not necessarily for DOIs since they become much harder to find in searches. For example, the Zotero lookup function does not work with such percent encoded DOIs.

It turns out that Zotero is using a non-default option in the underlying citeproc-js library to intentionally generate such percent encoded DOIs. This was introduced about 9 years ago in order to ensure that DOIs can be clicked on and opened as URLs. This has a benefit for online bibliographies but for regular use in bibliographies in publications it can lead to quite extensive manual fixing of generated content.

In my view, Zotero should follow the default behaviour of the underlying citeproc-js library or make the automatic conversion of DOIs into percent encoded URLs at least optional. A DOI is a unique identifier first which should not be modified. It is very useful to have it linked to an online resource directly but that is a secondary function.

It turns out that last year the DOI.org organisation requested and implemented a similar change to the default behaviour of citeproc-js which affects DOIs in the most minimal way possible. For example, '[]' charcters are not affected. This should make Zotero's use of the more heavy-handed non-default option of citeproc-js unnecessary.

Please see https://github.com/zotero/zotero/issues/5557 for more background and examples.

This change is in Zotero 8.0.1.