On 2 July 2011 20:55, Sascha Silbe si...@activitycentral.com wrote:
It does make sense, but it would be an incompatible API change.
Activities that don't use markup would need to handle the escaping for
Sugar = 0.92 and must not escape the text for Sugar 0.94+. Similarly,
activities that do
Excerpts from Daniel Drake's message of Mon Jun 27 13:24:14 +0200 2011:
On 26 June 2011 19:06, Sascha Silbe si...@activitycentral.com wrote:
While chasing down a similar bug in the Clock Frame device, I noticed that
we're lacking the necessary escaping in most of Sugar. See SL#2099 for an
On 26 June 2011 19:06, Sascha Silbe si...@activitycentral.com wrote:
While chasing down a similar bug in the Clock Frame device, I noticed that
we're lacking the necessary escaping in most of Sugar. See SL#2099 for an
example of what can happen if we don't.
This patch series only covers
While chasing down a similar bug in the Clock Frame device, I noticed that
we're lacking the necessary escaping in most of Sugar. See SL#2099 for an
example of what can happen if we don't.
This patch series only covers Palette primary/secondary text and MenuItem
labels. There's a good chance text
4 matches
Mail list logo