https://bugs.kde.org/show_bug.cgi?id=364030

Thomas Fischer <fisc...@unix-ag.uni-kl.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://mirrors.ctan.org/inf
                   |                            |o/bibtex/tamethebeast/ttb_e
                   |                            |n.pdf
         Resolution|---                         |WAITINGFORINFO
      Latest Commit|                            |81f383f0eab238e1772e4ea996e
                   |                            |e39b954ffd4fd
             Status|CONFIRMED                   |RESOLVED

--- Comment #1 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> ---
> This used to work.
Handling of quotation marks was broken in special cases, and as such curly
brackets got enforced.

The problem is due the fact that KBibTeX could not handle cases where the
user's text (title, author, ...) contained quotation marks. For example, a
title like 'A "B" C' would have been written as
title = "A "B" C"
which is invalid. To avoid such problems, curly brackets got enforced when
writing .bib files.

As of commit 81f383f0eab238e, currently only available on my private repository
[1] in branch bugs/kde364030, KBibTeX will try to detect those problems and
will write the title as follows:
title = "A {"}B{"} C".

This is the supposed behaviour as of described in "Tame the BeaST" (p. 20) [2].

Please test the commit referred to above to confirm if the problem is fixed for
you.

> Linked to that, other options on the panel are not remembered.
> For example, I have un-ticked the protect casing option (I do that
> myself if needed) and it comes back the next time I open kbibtex.
That is a different problem I am going to investigate next.

[1] https://quickgit.kde.org/?p=clones%2Fkbibtex%2Fthomasfischer%2Fkbibtex.git
[2] http://mirrors.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to