To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51772
------- Additional comments from f...@openoffice.org Mon Jan 5 14:08:18 +0000 2009 ------- @ayaniger: Well, for issue 16354 I already implemented some code that changes the script type obtained from i18n to COMPLEX in case the direction of the character run is RTL, see porlay.cxx. For a couple of tasks (e.g., spell checking, word count etc.) the SwScanner::NextWord method is used. This method contains some code that clips the words at script type boundaries. Now in my opinion the problem is that the SwScanner::NextWord function does not use the ScriptInfo data structure (which contains the 'changed' script type) but rather directly used the break iterator to find the script boundaries. What do you think? --------------------------------------------------------------------- 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: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
