Issue 96045 - Enable CTL (Arabic, Persian etc.) Support for AutoCorrection
Summary: Enable CTL (Arabic, Persian etc.) Support for AutoCorrection
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOO300m9
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords:
: 90473 (view as issue list)
Depends on:
Blocks: 95322
  Show dependency tree
 
Reported: 2008-11-10 10:47 UTC by weko
Modified: 2013-08-07 14:43 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description weko 2008-11-10 10:47:32 UTC 
In order to solve the AutoCorrection problem reported in Issue 95322 we need CTL 
support for OOo AutoCorrection.
Comment 1 Oliver Specht 2008-11-11 09:54:06 UTC 
Fixed in cws os123 in 
svx/source/dialog/autocdlg.cxx
Comment 2 weko 2008-11-24 09:21:19 UTC 
.
Comment 3 weko 2008-11-24 09:23:35 UTC 
*** Issue 90473 has been marked as a duplicate of this issue. ***
Comment 4 Oliver Specht 2008-12-10 09:22:59 UTC 
Reassigned for verification
Comment 5 michael.ruess 2008-12-11 13:47:27 UTC 
MRU->SBA: please check this in CWS os123.
Comment 6 stefan.baltzer 2008-12-18 08:21:06 UTC 
Verified in CWS os123.

Note: This issue is flagged "Feature", but has no real UI change. It "only"
brings more (already translated) CTL language entries in the AutoCorrect dialog
language list. 
Therefore this is NOT a feature in terms of specification and translation. "Make
AutoCorrection work (for CTL language) as it works for all Western languages
already" can
be even regarded as a defect: A  rightful user expectation ("support my
language") got fixed. So no special new test plan is needed for this, see also
issue 95322.
Comment 7 thorsten.ziehm 2010-02-22 14:47:09 UTC 
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  :
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues