-
Notifications
You must be signed in to change notification settings - Fork 31
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
url field needs special filter:latex treatment - at least, for jekyll-scholar #105
Comments
you're absolutely right. we should add a list of excluded fields for each filter to tackle such issues. |
The special meaning of |
Related to this: I have a number of review-entries in my bibliography which include
|
Not sure what you mean by 'escape' exactly? |
Sorry for the lack of clarity. I am using Currently, it outputs as |
You'll have to add your own filter, because the filters used by |
Another common character in URLs is the tilde, often before the username for as in something like http://some-university.edu/~username/ . Currently, the latex filter will translate this tilde into a non-breaking space, and break the url. Is there an easy way around this? |
I know it is quite late. Just for reference is someone is directed to this issue by google search. To use tilde in URL we can use Latex syntax. For the above example, this should work http://some-university.edu/\~{}username/ |
can you give an example for how I'd make a filter for this issue with the tildes? update: I ended up adapting the code from @iiegn (https://github.com/iiegn/iiegn.eu-jekyll-site/blob/master/_plugins/jekyll-scholar.rb), replaced _ with ~. Seems to work. |
a somewhat special(tm) url field entry of the form
url = {http://some.where/foo\_--\_bar}
becomeshttp://some.where/foo_–_bar
(the dash here being an en dash now).i came across this while using jekyll-scholar but found the root of the problem to be here, i think. at first, i thought just deactivating the latex filter for the url field would solve the problem but then again
\_
should be processed.The text was updated successfully, but these errors were encountered: