[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 --- Additional comments from h...@openoffice.org Wed Jun 30 08:53:05 + 2010 --- Status update: When ICU's http://bugs.icu-project.org/trac/ticket/7772 (Fast string direction detection) is resolved the method getDefaultDirection() could be implemented more directly using that new ICU call, if OOo's ICU baseline had it available. - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 User erack changed the following: What|Old value |New value Target milestone|OOo 3.3 |OOo 3.x --- Additional comments from er...@openoffice.org Wed Feb 24 19:53:06 + 2010 --- Fruit flies like banana.. retargeting to OOo3.x, should actually be OOo3.4 but that target doesn't exist yet. - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 --- Additional comments from er...@openoffice.org Sat Aug 22 19:41:13 + 2009 --- @hdu: A rewrite to directly use ICU sounds indeed most promising. Thanks for the thought. - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 --- Additional comments from h...@openoffice.org Thu Aug 20 06:08:50 + 2009 --- @erack: the idea behind this method is just to find the first codepoint in the string with strong bidi- direction properties. Since icu is already available in i18npool and its u_charDirection() method is cheap there is probably not much need for fancy caching directly or indirectly (by tunneling the cache of all character properties cache from other modules). - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 --- Additional comments from h...@openoffice.org Thu Aug 20 06:48:43 + 2009 --- Splitting the method getDefaultDirection() off is probably a good idea too. - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 85360] Move implementation of App lyLreOrRleEmbedding() to i18npool ApplyNatural BidiEmbedding() (was: Wrong BiDi-behavior for composed strings)
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=85360 User erack changed the following: What|Old value |New value Issue type|DEFECT|TASK Summary|Wrong BiDi-behavior for co|Move implementation of App |mposed strings|lyLreOrRleEmbedding() to i | |18npool ApplyNaturalBidiEm | |bedding() (was: Wrong BiDi | |-behavior for composed str | |ings) Target milestone|OOo 3.2 |OOo 3.3 --- Additional comments from er...@openoffice.org Wed Aug 19 22:09:42 + 2009 --- Looking into moving the implementation of ApplyLreOrRleEmbedding() down to i18npool I encountered some obstacle. The implementation takes advantage of SvtSysLocale to obtain a cached character classification at almost no cost. That is not available in i18npool, and we certainly don't want to create new instances of XCharacterClassification for each string inspection, so would need some cached instance there as well and refactor some coding details. Nothing hard to implement, just doesn't fit into my schedule for OOo3.2, therefor retargeting to OOo3.3. Anyway, according to 'hdu' the original bug is fixed with ApplyLreOrRleEmbedding(), so I'm setting the issue type to TASK. However, best would even be if SvtSysLocale could pass the cached instances down to i18npool instead of having to create another instance there. - 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...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
