THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#750 - Pango markup in menus does not work
User who did this - Matthias Schroeder (murphy42)
----------
OK, now i understand your concerns, yes i also think it's users concern to do
the appropriate escaping, in typical use cases it should be no problem:
menu_from_scripted_curious_source | util.escape > menu.new
or
menu_from_scripted_curious_source | util.escape | script_to_add_smart_accesskey > menu.new
and with hand written menu it should be no problem either.
The question remains which char we should use for access-key - it should be a
char which has a valid quoted version to get it in the menu-string as himself
naturally, so we can choose from and force users to use the quoted version
whenever he wants to use this char literally
' " < > & -
(at least i have no idea how to easily distinguish between _ as access key
marker und _ literally (or any other char we choose))
how about the <u>CHAR</u> version? Easy to substitute and remember, breaks
nearly nothing, just a bit - uhm, i don't like it ;)
besides: The users problem was introduced cause my first version to introduce
access keys was too naive - i think second version is better but maybe not very
lua- like.
Just an idea a little bit off topic: should/could we replace menu.item.text with pangos err message?
----------
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=750#comment1898
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to [email protected].
