Skip to content

chaning to relative path does not work and prevents convertion to biblatex #6223

@JoKalliauer

Description

@JoKalliauer
JabRef 5.1--2020-03-23--67daf36
Windows 10 10.0 amd64 
Java 14
% Encoding: UTF-8

@Article{kauert2011direct,
  author    = {Kauert, Dominik J. and Kurth, Thomas and Liedl, Tim and Seidel, Ralf},
  journal   = {Nano Letters},
  title     = {Direct mechanical measurements reveal the material properties of three-dimensional {DNA} origami},
  year      = {2011},
  issn      = {1530-6984},
  month     = dec,
  number    = {12},
  pages     = {5558--5563},
  volume    = {11},
  adsnote   = {Provided by the SAO/NASA Astrophysics Data System},
  adsurl    = {http://adsabs.harvard.edu/abs/2011NanoL..11.5558K},
  doi       = {10.1021/nl203503s},
  file      = {:../../Literature/DNA/Kauert_Kurth_Liedl_Seidel_2011_Nano letters_Main.pdf:PDF;:../../Literature/DNA/Kauert_Kurth_Liedl_Seidel_2011_Nano letters_SupportingInfo.pdf:PDF;\:..\\\\..\\\\Literature\\\\DNA\\\\Kauert_Kurth_Liedl_Seidel_2011_Nano letters_Main.pdf\:PDF\;\:..\\\\..\\\\Literature\\\\DNA\\\\Kauert_Kurth_Liedl_Seidel_2011_Nano letters_SupportingInfo.pdf\:PDF:\:../../Literature/DNA/Kauert_Kurth_Liedl_Seidel_2011_Nano letters_Main.pdf\:PDF\;\:../../Literature/DNA/Kauert_Kurth_Liedl_Seidel_2011_Nano letters_SupportingInfo.pdf\:PDF:PDF},
  groups    = {DNA, YoungsModulus, DNAOrigami},
  keywords  = {rank1},
  publisher = {ACS Publications},
  ranking   = {rank1},
}

@Comment{jabref-meta: databaseType:bibtex;}

Steps to reproduce the behavior:

  1. open bibtex2biblatexBug.bib.txt
  2. clean up using following settings
    Screenshot 2020-03-31 18 57 27

nothing happens (also journal should be converted to journaltitle) and if you mark several files no file (after that file) get changed. (No warning no errormessage)

If I disable "change to relative path" it works again.

The strange thing you newer know it just needs some time or it does not work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    component: cleanup-opsstatus: staleIssues marked by a bot as "stale". All issues need to be investigated manually.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions