geodes-sms / relis

Tool for conducting systematic literature reviews and mapping studies
http://relis.iro.umontreal.ca/
GNU General Public License v3.0
20 stars 16 forks source link

Importing bibtex strips latex commands for accented characters #23

Open in-the-mood-for-mov opened 4 years ago

in-the-mood-for-mov commented 4 years ago

Describe the bug Accented characters are represented as latex commands in bibtex files. Relis simply strips the braces and backslashes.

To Reproduce Import a bibtex entry such as this one

@phdthesis{logre2017preserver,
  title={Pr{\'e}server la S{\'e}paration des Pr{\'e}occupations durant l'Int{\'e}gration de Domaines H{\'e}t{\'e}rog{\`e}nes dans les Syst{\`e}mes Logiciels.(Preserving Separation of Concern while Integrating Heterogeneous Domains in Software Systems).},
  author={Logre, Ivan},
  year={2017},
  school={University of C{\^o}te d'Azur, France}
}

Expected behavior The title is displayed as Préserver la Séparation des Préoccupations durant l'Intégration de Domaines Hétéogènes dans les Systèmes Logiciels.

Screenshots

image

Desktop:

Additional context This happens on the instance hosted at http://relis.iro.umontreal.ca.

in-the-mood-for-mov commented 4 years ago

I can try to fix it myself. Are there instructions to setup relis on my machine?

esyriani commented 4 years ago

@bricemike1 There is a new version of BiBler that may solve this issue. Just replace the src/bibler with the new version at https://github.com/geodes-sms/bibler/tree/master/src/bibler. Note, however, it needs Python 3.7 or later on the server.

in-the-mood-for-mov commented 4 years ago

Another issue with bibtex parsing is that it does not handle the braces to escape text. I used a bibtex file from Web of Science, which has entries such as

Year = {{2019}},
DOI = {{10.1017/S0956796819000169}},

I get the following result.

image Capture d’écran, le 2020-04-30 à 10 29 52

Please tell me if I should file this issue with BiBler instead.

esyriani commented 4 years ago

Hi @kolmogorov-fan-account , yes this is a BiBler issue. We can include this fix in the next release of BiBler. We can then update ReLiS will the latest version of BiBler.