To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=17171
------- Additional comments from [EMAIL PROTECTED] Thu Nov 8 19:14:43 +0000 2007 ------- Folks, can we move that discussion elsewhere? The poor developers that later on will work on that issue will have problems to find relevant information in this "chat". It's clear that 64KB for a paragraph is not enough and the OOo UNO API already uses 32Bit whereever text is retrieved from a text object (e.g. paragraphs, portions, selections etc.). This is not related to how a paragraph stores its text internally. This way how the text is stored in the implementation is not the problem of this issue. We have an *internal C++ API* that is limited to 16Bit and *this* must be fixed. And the problem is that this API is so widespread in OOo. The *external API* (UNO API) uses 32Bit and this will not be changed without a valid reason. The ability to store the whole Encyclopedia Britannica, the Wikepedia and the whole Google cache into a single paragraph is *not* a valid reason. So please try to add only comments that describe new, currently unknown situations where the 64KB limit bites users (situations that are not described in this issue or its duplicates). Thank you. --------------------------------------------------------------------- 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]
