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

Store LaTeX-free version inside each BibTeX entry #518

Closed
stefan-kolb opened this issue Dec 15, 2015 · 8 comments
Closed

Store LaTeX-free version inside each BibTeX entry #518

stefan-kolb opened this issue Dec 15, 2015 · 8 comments

Comments

@stefan-kolb
Copy link
Member

stefan-kolb commented Dec 15, 2015

Each bibtex entry should store a latex-free version of its fields for searching and passing to search engines/downloader/general search/... Add wrapper to be able to change default returns of getField to latex-free version of the field value. Probably useful for all fetchers to get correct results.

@oscargus
Copy link
Contributor

Should this field be UTF-8 or how should non-ASCII characters be handled? Should it be stored it the .bib-field or dynamically generated?

@keinstein
Copy link

I'd suggest to use the internal Java Unicode encoding. if I understand stefan-kolb right he wants to have a clean and easy to use API. Caching would improve the performance at the cost of memory. May be it can be made configurable? If the cache value exists hand it out, otherwise check whether the caching bit is set and save the generated value in the cache. The performance-hit should not be very large.

@koppor
Copy link
Member

koppor commented Feb 21, 2016

+1 for internal Java Unicode encoding which should be equal to UTF-8 and +1 for caching. No storage in the fields read or written by BibtexParser or BibEntryWriter.

Refs #161.

@koppor koppor changed the title Store LaTeX-free version inside each BibTex entry Store LaTeX-free version inside each BibTeX entry Feb 21, 2016
@oscargus
Copy link
Contributor

Just noting that this sort of functionality (minus the caching) have been sort of implemented in the new and improved main table renderer.

stefan-kolb added a commit that referenced this issue May 25, 2016
@stefan-kolb
Copy link
Member Author

See #1252

@stefan-kolb stefan-kolb added this to the v3.5 milestone May 31, 2016
@stefan-kolb stefan-kolb removed this from the v3.6 milestone Aug 3, 2016
@koppor koppor added this to the v3.7 milestone Aug 18, 2016
@koppor koppor removed the stupro label Sep 12, 2016
@stefan-kolb stefan-kolb removed this from the v3.7 milestone Sep 28, 2016
@koppor
Copy link
Member

koppor commented Sep 29, 2016

I think, this is implemented in #2091.

@stefan-kolb
Copy link
Member Author

In a way, but not properly.

@lenhard
Copy link
Member

lenhard commented Oct 3, 2016

Is implemented in #2102

@lenhard lenhard closed this as completed Oct 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants