Hi Andrew, Markup uses tags like "<color=#fff> hello </color>". It is clear why it's essential to do "character escaping" like ">" instead of "<". Otherwise, if you feed "<" back to the entry widget, it will be misinterpreted as a tag element. As a side note, you can use "elm_entry_markup_to_utf8" helper to strip-down the formatting and "un-escape" the characters so all becomes a valid utf8 text.
Hope that clears things up a bit. -- Danny (herdsman) Hirt On Sun, Jun 18, 2017 at 11:18 PM, Andrew Williams <a...@andywilliams.me> wrote: > Hi team, > > Netstar pointed out something to me today that I had completely missed for > ages - elm_entry assumes you are typing markup. Type "a>b" and text_get > will return "a>b" - what is the reason for this? It seems completely > crazy default behaviour. > Is there any reason we can't turn this off by default but provide the > markup filter in a way where it can be switched on as needed? > > Thanks, > Andy > -- > http://andywilliams.me > http://ajwillia.ms > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
