Setting limits of this kind is an engineering trade off. The limit for titles is 50 bytes. Surely, the limits should be long enough to contain the examples in the "Writer Guide". The sample bibliography in Chapter 12 "Tables of Contents, Indexes, and Bibliographies" uses four examples. Of the titles there, one: "A Conceptual Guide to OpenOffice.org 2 for Windows and Linux" is too large and a second "Learn OpenOffice.org Spreadsheet Macro Programming" is at the limit of 50 characters. Follow the following steps: Tools->Bibliographic Database Insert->Record Enter an identifier: GUR00 Enter an author: Gurley, Gabriel Enter the title: A Conceptual Guide to OpenOffice.org 2 for Windows and Linux Enter a year: 2000 Tab past the last field File->Close Window An error dialog appears with a message reading: "The string 'A Conceptual Guide to OpenOffice.org 2 for Windows and Linux' exceeds the maximum length of 50 characters when converted to the target character set 'utf-8'."
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
no problem in LibO 3.5.0 beta on Fedora 64 bit but in LibO 3.6.0 master from 1 feb 2012 appears strange characters in some fields
@ Allan Jacobs Please, verify if in last version of LibreOffice still reproducible
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian