On Wed, 2012-12-05 at 10:52 +, Jack Leigh wrote:
> > I wonder - could we not provide some compile-time lint tool for this to
> > catch & warn/fail on bad strings ? presumably that would solve the
> > problem permanently in a way that doens't require lots of ongoing
> > care ? :-)
>
> Also
I wonder - could we not provide some compile-time lint tool for this to
catch & warn/fail on bad strings ? presumably that would solve the
problem permanently in a way that doens't require lots of ongoing
care ? :-)
Also are they 3 stops or unicode ellipsis? This would also catch that.
On Mon, 2012-12-03 at 21:56 +0100, Sophie Gautier wrote:
> Just a tiny note for the quality of the en_US version: when a string in
> a menu is followed by 3 dots -> there is no space between the string and
> the dots.
Heh :-)
> I didn't fill any issue about this, but may be keep it in mi
Dear developers,
Just a tiny note for the quality of the en_US version: when a string in
a menu is followed by 3 dots -> there is no space between the string and
the dots.
I didn't fill any issue about this, but may be keep it in mind when you
meet such a string :)
Kind regards
Sophie
--
Sophie
