Issue 34050 - alternative way of entering unicode characters
Summary: alternative way of entering unicode characters
Status: CONFIRMED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1.2
Hardware: PC Windows XP
: P5 (lowest) Trivial with 7 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-09-10 09:48 UTC by jigal
Modified: 2013-02-07 22:40 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 jigal 2004-09-10 09:48:26 UTC 
One can only enter Unicode characters that are not assigned to ALT+nnnn codes 
by using the Insert Special Character dialog.
In various Microsoft apps it's possible to enter the four digit hexcode 
followed by ALT+X which converts the code into the unicode character.
CTRL+SHIFT+X converts a unicode character on the left of the cursor into its 
hexadecimal representation.
This is very handy for entering a few well known characters very often.
Not a big issue, but also not very hard to implement IMHO.
Comment 1 stefan.baltzer 2004-09-14 17:28:29 UTC 
SBA: Reassigned to BH.
Comment 2 peschtra 2004-12-19 20:45:40 UTC 
There is an extremely large amount of confusion over this topic. It would be
nice if it could be implemented or addressed.

Still true in 1.1.4RC.
Comment 3 jigal 2005-10-07 10:34:18 UTC 
And still true in 2.0Beta (1.9.130) :-(
Comment 4 jwt 2006-12-06 12:01:21 UTC 
This seems to be the same as Issue 66097 for OOo 2.0.3.
Comment 5 bettina.haberer 2010-05-21 14:55:50 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".
Comment 6 philipp.lohmann 2010-07-22 19:46:09 UTC 
This is not the same as issue 66097; that one and related issues are about
direct input. This one (as far as I understand) requests to input normal
character sequences (e.g. "bfa6"), then press Ctrl+Shift+x to convert that
sequence left of the cursor and replace it by the corresponding unicode (in the
example 0xbfa6).

The difference is where the conversion is done, either in input itself of
afterwards by the application.