-
Notifications
You must be signed in to change notification settings - Fork 281
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
Removing rich text formatting from title string #585
Open
domiden
wants to merge
18
commits into
jlegewie:master
Choose a base branch
from
domiden:dev-rich-text-formatting
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make clear that this repo is under development
…truncation of long titless
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scientific publications are often using (font) formatting such as italic, bold, etc. to satisfy regulations, which are required by specific codices. For example, scientific species names formatted italic, such as "Triticum aestivum subsp. aestivum" (common wheat) or "Berberis spp." To achieve that for the publication title,
Zotero
allow using rich text formatting based onHTML
code. But if titles have been already formatted,ZotFile
just remove special characters defined bywildcard.js
or a user-specific wildcard have to be implemented, which isn't that user-friendly. It is highly likely, that this user case doesn't concern just a few people, and therefore I suggest including this additional replacement rule into thewildcard.js
.I think, there is no need to include a (GUI) preference option.
Example
Formatted title:
Expected result:
Result with current
ZotFile
version (1ad811a, 688c423):(Where just the special characters
"
,<
, and>
have been replaced, but not all theHTML
syntax.)