https://bugzilla.novell.com/show_bug.cgi?id=691572
https://bugzilla.novell.com/show_bug.cgi?id=691572#c36
Duncan Mac-Vicar changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
CC| |dmacvicar@suse.com,
| |ma@suse.com
InfoProvider|dmacvicar@suse.com |
--- Comment #36 from Duncan Mac-Vicar 2012-07-18 15:16:54 UTC ---
I don't think libzypp is the right place for this. But also not the job of the
concrete UI implementations.
Giving the fact that our current YRichText::setText() implementation assumes
you are giving (simplified) HTML (unless setTextMode() is enabled) I would keep
the magic in this area. Therefore libyui currently assumes that a concrete UI
Foo implementation is handling HTML in FooRichText.
I would add a C/C++ markdown parser to libyui, and modify setText so that if
<!-- DT:Rich --> is found at the beginning then the text is set "as is"
(assumed HTML). We can detect it in other ways as well. Also, AFAIK, html is
valid markdown, so we could just process the text always.
If not, we assume it is markdown, and process the text. We need to verify that
ncurses can cope with the markdown parser HTML output, or at least it can
ignore the unknown tags.
If setTextMode is enabled and the text does not contain <!-- DT:Rich --> then
we set the text unprocessed.
Now, IIRC, the Qt selector does not use the libyui widget, but the ncurses one
does, right?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.