Issue 99397 - UNX: implement IsKashidaPosValid()
Summary: UNX: implement IsKashidaPosValid()
Status: ACCEPTED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOO310m1
Hardware: Mac All
: P3 Trivial (vote)
Target Milestone: OOo 3.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 08:53 UTC by hdu@apache.org
Modified: 2017-05-20 11:35 UTC (History)
2 users (show)

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

Attachments
bugdoc from i99295 (thank you hennerdrewes!) (8.25 KB, application/vnd.oasis.opendocument.text)
2009-02-19 09:05 UTC, hdu@apache.org 		no flags Details
screenshot from CWS ooo31gsl2 (4.13 KB, image/png)
2009-02-19 09:06 UTC, hdu@apache.org 		no flags Details
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 hdu@apache.org 2009-02-19 08:53:40 UTC 
Followup to issue 22925#20: For dealing with certain text+font combinations IsKashidaPosValid() needs to 
be implemented so that non-expandable glyph combinations do not get involved in kashida justification.
Comment 1 hdu@apache.org 2009-02-19 09:05:14 UTC 
Created attachment 60298 [details]
bugdoc from i99295 (thank you hennerdrewes!)
Comment 2 hdu@apache.org 2009-02-19 09:06:42 UTC 
Created attachment 60299 [details]
screenshot from CWS ooo31gsl2
Comment 3 hdu@apache.org 2009-03-04 14:28:06 UTC 
.
Comment 4 hdu@apache.org 2010-08-09 11:34:47 UTC 
On the OpenType list an interesting point was raised today for this topic:
> a Naskh-like font will have a totally different set of "legal" insertion points than a Nastaliq-like font
Comment 5 Marcus 2017-05-20 11:35:19 UTC 
Reset assigne to the default "issues@openoffice.apache.org".