Menu

#103 annote: BibDesk 0.94 displays {\par} as {\par} on the screen

closed-duplicate
File I/O (232)
5
2004-06-26
2004-04-30
Markus Gail
No

There's another bug in the "annote" panel: BibDesk 0.94 displays
{\par} as {\par} on the screen, other characters as well, e. g.
German umlauts like {"u}

Discussion

  • Markus Gail

    Markus Gail - 2004-04-30
    • assigned_to: nobody --> mmcc
     
  • Adam Maxwell

    Adam Maxwell - 2004-05-01
    • assigned_to: mmcc --> jameshowison
     
  • Adam Maxwell

    Adam Maxwell - 2004-05-01

    Logged In: YES
    user_id=732757

    assigning James on this one so he can comment. I think he
    looked into this {\par} issue, but I don't remember the details
    on it.

    Markus, what is the end result that you want in BibDesk and
    in BibTeX?

     
  • Adam Maxwell

    Adam Maxwell - 2004-05-01

    Logged In: YES
    user_id=732757

    assigning James on this one so he can comment. I think he
    looked into this {\par} issue, but I don't remember the details
    on it.

    Markus, what is the end result that you want in BibDesk and
    in BibTeX?

     
  • James Howison

    James Howison - 2004-05-01

    Logged In: YES
    user_id=844653

    Marcus, I tried to get the par and linebreaks converted properly a while
    ago but managed to break some other stuff in the process. So I wound it
    out. Now I realize I probably also turned off the proper conversion of the
    other characters.

    I'll look at this tonight.

    Does this mean that you care about retaining linebreaks from the Annote
    editor right through to latex production? ie. are you using the annote field
    in a latex document, or just using Bibdesk as a database for your
    annotations?

     
  • Adam Maxwell

    Adam Maxwell - 2004-05-01

    Logged In: YES
    user_id=732757

    sorry for the duplicate posts. OmniWeb 5b4 worked great,
    but 5b5 has broken caching. grr.

    James, you didn't disable conversion of other characters;
    BDSKConverter is working fine for stuff in the dictionary.
    I just don't remember what broke in the newline conversion.

     
  • Markus Gail

    Markus Gail - 2004-05-02

    Logged In: YES
    user_id=964393

    > Does this mean that you care about retaining linebreaks from the
    Annote
    > editor right through to latex production? ie. are you using the annote
    > field in a latex document, or just using Bibdesk as a database for
    > your annotations?

    No, I don't use the annotations in my LaTeX documents. The annotations
    are just for my own information. The errors occured when I moved lots
    of plain text files to the database through the clipboard. Most of the text
    files were produced in Mac OS 8 and surely had no Unix line breaks.
    After that, BibDesk refused to open my .bib database.

     
  • Markus Gail

    Markus Gail - 2004-05-02

    Logged In: YES
    user_id=964393

    > Markus, what is the end result that you want in BibDesk and in BibTeX?

    BibDesk should automatically encode all special characters correctly
    whatever I copy to the "annote" panel. I don't know if {\par} is allowed
    in the BibTeX syntax. If so, BibDesk should convert all the various Unix
    and Mac OS Classic carriage returns, line feeds, etc. to {\par}.

     
  • Adam Maxwell

    Adam Maxwell - 2004-05-02

    Logged In: YES
    user_id=732757

    This Mac/Unix linebreak conversion happens automatically,
    I think, just due to the OS X pasteboard.
    Stuff like umlauts will get converted when the file
    is saved, then will still appear as an umlaut when the file
    is reopened in BibDesk.

    Please post an example of the plain text that you're pasting in, so
    we can reproduce this, and also a .bib file (even one item)
    that shows the errors (refusal to open).

     
  • Adam Maxwell

    Adam Maxwell - 2004-06-26
    • status: open --> closed-duplicate
     
  • Adam Maxwell

    Adam Maxwell - 2004-06-26

    Logged In: YES
    user_id=732757

    Closing this bug, since it's really a duplicate. Perhaps someday
    we'll come up with a really great solution for this....

     

Log in to post a comment.

MongoDB Logo MongoDB