Issue 62291 - recognition of non-unicode custom characters and features
Summary: recognition of non-unicode custom characters and features
Status: CLOSED DUPLICATE of issue 4638
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: current
Hardware: All Windows XP
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2006-02-20 00:46 UTC by aoku
Modified: 2006-02-22 22:08 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
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 aoku 2006-02-20 00:46:29 UTC 
Some fonts are using non-unicode characters and features such as ligatures, 
mark positioning or contextual alternates to automatically transform a defined 
succession of glyph into another single glyph. Here are some example :
"f f i" => single glyph of the ligature "ffi"
"o e" => glyph "Å“" (this one is an unicode ligature, works for french "Å“uf")
"[any small letter] s" normal zigziging s
"[any] s [any small letter]" bar old "s", especially used for "st" or "sd"
(arab wordprocessing with final, initial, isolated and medial forms is another 
revelant example, some of them are coded in unicode, and some other not)

The non-unicode features are not recognized by OpenOffice (tested 
in "Writer"), as in most of winXP compatible word processors (apart from 
BabelPad). It would be quite nice if the word processor would handle such non-
unicode combinations of glyph. I'm not sure of it, but without this ability, 
some languages which have no unicode-defined locations (perhaps Tibetan, Urdu, 
Bengali, Farsi, this list is not exhaustive) for their accented 
characters/ligatures/other features cannot be displayed properly.

Another argument in favor of an enhancement would be that OpenOffice do not 
use the entire possibilities of fonts with OTL tables.
Comment 1 aoku 2006-02-20 00:50:55 UTC 
It seems that "oe" character was not recognized either in my report, so I put 
it in unicode :
"U+006F U+0065" => "U+0153"
Comment 2 michael.ruess 2006-02-20 07:37:19 UTC 
Reassigned to SBA.
Comment 3 lohmaier 2006-02-22 22:05:29 UTC 
OOo perfectly can handle ligatures. It is only that you have to enter them
yourself since:
1) OOo doesn't replace them automatically while typing
2) OOo doesn'T come with a font that actually contains these ligatures.
4) Spellcheck-dictionaries don't accout for ligatures (most of them)
5) Not every combination of letters that can be combined to a ligature must be
turned into a ligature every time.

All the above makes this a difficult task. Furthermore it is a duplicate


*** This issue has been marked as a duplicate of 4638 ***
Comment 4 lohmaier 2006-02-22 22:05:44 UTC 
closing duplicate.
Comment 5 lohmaier 2006-02-22 22:08:20 UTC 
If you have concrete examples of ligatures that don't work, then please file
seperate issues for them, with sample document (and screenshot)