Opened 9 years ago
Last modified 6 years ago
#635 new enhancement
In-content translator
| Reported by: | dstillman | Owned by: | nobody |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | ingester | Version: | 1.5 |
| Keywords: | helpwanted | Cc: | simon, stakats |
Description
http://forums.zotero.org/discussion/822/
Whether or not we include this by default would depend on the performance hit, but it may be fine.
Change History (6)
comment:1 Changed 9 years ago by stakats
comment:2 Changed 9 years ago by dstillman
Well, that might make more sense for performance reasons, but wouldn't it be preferable to have automatic detection through detectWeb() if feasible? It's possible there could be a meta translator that ran a single regex for the various formats in detectWeb and passed off the match to the respective translator.
comment:3 Changed 9 years ago by dstillman
If implemented, this might also help with #539.
comment:4 Changed 9 years ago by dstillman
- Cc stakats added
- Milestone changed from 1.0 RC 4 to 1.5 Alpha 1
- Summary changed from BibTeX-in-content translator to In-content translator
- Version changed from 1.0 to 1.5
Whatever solution we choose should work for all import formats (and, by request, MARC records too).
comment:5 Changed 7 years ago by dstillman
comment:6 Changed 6 years ago by dstillman
- Milestone 2.0 Beta 3 deleted
Milestone 2.0 Beta 3 deleted
Why not allow the selection of any text to run through our import routine, checking against all available import translators? Then users could highlight inline RIS data, etc. BibTeX would probably be the most commonly used, but the feature might as well be open to others.