У пон, 20. 09 2010. у 18:10 +0000, Nicolas Delvaux пише:
> Do you really need that a project as huge as Gnome starts to use nnbsp
> widely to just implement a fix?

It's not a fix: it's a feature request.  Launchpad fully supports nnbsp.
You are just having trouble inputting it, and I haven't seen conclusive
evidence suggesting browsers don't support it.

> (anyway, I will argue in favour of it's adoption in Gnome at the
> beginning of the next cycle)

Excellent.  Please let us know how it goes.

> Otherwise, I also noticed that there is in fact no easy way to input a
> nnbsp with Windows (it requires to mess around with REGEDIT...) and
> also that there is no short-cut for it on GNU/Linux with a Canadian
> layout (I have to verify this last one).
> So we really need a tag such as [nbthin] to workaround those input
> problems.

I am simply not convinced: as someone who has worked on Serbian
localization from the ground-up for free software, I am familiar with
what it takes to get special characters supported in translations.  For
instance, Serbian uses „these“ kind of quotes.  No keyboard layout other
than the Serbian keyboard layouts in XFree and X.org support it (which I
helped develop).  The way to fix a problem of the missing characters is
to enable their input: if the character is the right one to use, why
should you not use it as part of your daily input in French?  (if you
don't like my example, think of many other Unicode characters that are
typographically more appropriate for text, but rarely used: em- and
en-dashes, minus, ellipsis, etc)

Is it not something that could be automatically produced instead?  For
example, perhaps a simple post-processing step on French .po files
export would do the trick?  Would such post-processing be possible (iow,
is it well defined)?

If something is supposed to be a better way of doing things, then we
should not limit that feature to Launchpad.  Entire free desktop stack
should benefit from it.  If it's missing in Canadian layout, perhaps
that's where it needs to be added first.

> The patch I submitted just add 6 lines to the code (I don't take
> documentation into account).

The patch you submitted is not really complete.  And it touches stuff it
shouldn't touch.  But, I am sure we can get it in order for landing.
And then, if it ends up in Launchpad, what's to guarantee that:
 - it will receive widespread use
 - we'll know what to do with it in the future
 - we won't keep getting requests for characters for specific languages
simply because people don't want to solve the problem at the right level
(i.e. keyboard input)

> The code is the same that with other tags, so I can't imagine how it
> can break something that may have not break without it.

A reminder: [nbsp] was introduced because of browser bugs. [tab] is
there because TAB key switches you to the next input field on a web
form.

> Could you please re-consider your opinion on this?
> 
As I stated earlier, we can perhaps consider having a "special way to
*display* nnbsp".  But, what about other spacing characters?  Why is
nnbsp more important than them?  For it to really become more important,
someone has to use them first :)

My opinion is that you can already start using Launchpad with nnbsp
characters.  You don't need to change Launchpad for GTK apps to benefit
from this.  You need to change translations for those apps.  I think it
would be less work for you to do that than to keep discussing this (this
bug is marked as affecting two people total).

I am sorry if you don't like my position, but I think I've clearly
explained what you can do to change it.  And you seem to be doing a good
job.  If I honestly saw Launchpad as a blocker to your efforts, I
probably would have gone out of my way to help you.  But, I repeat, you
can already add nnbsps inside Launchpad and via PO files.