Am 17.09.2010 um 11:39 schrieb Jean-Marc LASGOUTTES:
> Stephan Witt <[email protected]> writes:
>
>> But I have no problem to use only plain text instead. I'll change that.
>> It would become:
>>
>> 0x238b "{Escape}" "" "" "" # Qt::Key_Escape
>> 0x21e5 "{Tab}" "" "" "" # Qt::Key_Tab
>> 0x21e4 "{Backtab}" "" "" "" # Qt::Key_Backtab
>> 0x232b "{Backspace}" "" "" "" # Qt::Key_Backspace
>> 0x2326 "{Delete}" "" "" "" # Qt::Key_Delete
>> 0x2196 "{Home}" "" "" "" # Qt::Key_Home
>> 0x2198 "{End}" "" "" "" # Qt::Key_End
>> 0x21de "{Page Up}" "" "" "" # Qt::Key_PageUp
>> 0x21df "{Page Down}" "" "" "" # Qt::Key_PageDown
>> 0x21ea "{Caps Lock}" "" "" "" # Qt::Key_CapsLock
>>
>> or
>>
>> 0x21e4 "{Shift-Backspace}" "" "" "" # Qt::Key_Backtab
>> 0x21de "{Option-Up Arrow}" "" "" "" # Qt::Key_PageUp
>> 0x21df "{Option-Down Arrow}" "" "" "" # Qt::Key_PageDown
>>
>> What do you like best?
>
> I do not know. I would read the document I mentioned, that tells
> precisely how each key should be named in docs.
Then, I think the latter is the better.
And sorry, I meant:
0x21e4 "{Shift-Tab}" "" "" "" # Qt::Key_Backtab
> Why are the curly braces needed, actually?
I'm a fan of defensive implementations. (Don't know if this word exists.)
I want to avoid potential TeX errors when the output is not separated by
whitespace.
Is this impossible?
Stephan
