To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62664
------- Additional comments from [EMAIL PROTECTED] Fri May 19 03:36:27 -0700 2006 ------- Regina: I'm well aware of how UTF-8 behaves ;-) try 'man utf-8' on any recent Linux box to get an excellent write-up of all relevant terms. Either way - you are correct to say: > UTF-8 doesn't have a unique code length, for details see > http://www.unicode.org/reports/tr16/ Having said that - it *seems* that OO.o is happy to generate (by default) UTF-8 containing DB files - (I'm in an en_US.UTF-8 locale) - indeed, without the: <db:font-charset db:encoding="ibm850"/> in content.xml it seems to default to this; OTOH - we should clearly specify that. I guess - it's possible there is another ancilliary bug with field lengths & truncation when using UTF-8: entirely probable, but - at least with this approach we don't have the hideous performance penalty of loading & initializing the HSQLDB engine every time we want to simply add or insert a bibliography entry (surely?). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
