On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for so the patch still applies. I will resend the patch with a description that reflects that.
Le 12/03/2012 20:32, Christian Costa a écrit :
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for so the patch still applies. I will resend the patch with a description that reflects that.
BTW, is there an editor that shows them ? gvim doesn't. Non-breakable space are only present in french translations. Between a name and a ':'. This is not nicer to me. I wondering if that would not be better to remove them all...
On 03/13/2012 12:42 AM, Christian Costa wrote:
Le 12/03/2012 20:32, Christian Costa a écrit :
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for so the patch still applies. I will resend the patch with a description that reflects that.
BTW, is there an editor that shows them ? gvim doesn't.
I see them as normal space in vim but searching for a normal space doesn't highlight them. You can use the "highlight" and "match" command to show them in a different color.
Non-breakable space are only present in french translations. Between a name and a ':'. This is not nicer to me. I wondering if that would not be better to remove them all...
It doesn't matter if you consider them nicer or not. If they are required by the rules of the language then they will stay.
bye michael
2012/3/13 Michael Stefaniuc mstefani@redhat.com
On 03/13/2012 12:42 AM, Christian Costa wrote:
Le 12/03/2012 20:32, Christian Costa a écrit :
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for so the patch still applies. I will resend the patch with a description that reflects that.
BTW, is there an editor that shows them ? gvim doesn't.
I see them as normal space in vim but searching for a normal space doesn't highlight them. You can use the "highlight" and "match" command to show them in a different color.
Non-breakable space are only present in french translations. Between a name and a ':'. This is not nicer to me. I wondering if that would not be better to remove them all...
It doesn't matter if you consider them nicer or not. If they are required by the rules of the language then they will stay.
bye michael
With another version of gvim I have several charaters. That's not very practical. What a pity there is no explicit way to write it such as  , or \00C2\00A0 but hey.
Never heard of this rule for french or never paid attention but I'm fine with it if this is so. This string exists in native devenum and thus is subject to translation so I just have to find why regedit displays it badly when editing the registry. Wine traces functions also but I would it is more normal.
Christian
On Tue, Mar 13, 2012 at 11:52, Christian Costa titan.costa@gmail.com wrote:
Never heard of this rule for french or never paid attention but I'm fine with it if this is so.
Actually there should sometimes also be thin non-breakable spaces in po, but those are very badly supported, so are not used here.
Some links for your info: http://fr.wikipedia.org/wiki/Espace_typographique http://fr.wikipedia.org/wiki/Espace_ins%C3%A9cable (and other wikipedia pages) provide some information
This string exists in native devenum and thus is subject to translation so I just have to find why regedit displays it badly when editing the registry. Wine traces functions also but I would it is more normal.
Hmm... odd indeed
Frédéric
Am Dienstag, den 13.03.2012, 14:51 +0100 schrieb Frédéric Delanoy:
On Tue, Mar 13, 2012 at 11:52, Christian Costa titan.costa@gmail.com wrote:
This string exists in native devenum and thus is subject to translation so I just have to find why regedit displays it badly when editing the registry. Wine traces functions also but I would it is more normal.
Hmm... odd indeed
I think regedit uses the ANSI codepage for the registry, while the translations are in UTF-8. I experienced this when importing .reg-files in UTF-8 with special characters in them.
The umlauts in the German translation of regedit's GUI however, are displayed correctly. Is your nbsp part of the GUI or a registry-key? I would guess the second.
Le 14/03/2012 03:08, Julian Rüger a écrit :
Am Dienstag, den 13.03.2012, 14:51 +0100 schrieb Frédéric Delanoy:
On Tue, Mar 13, 2012 at 11:52, Christian Costatitan.costa@gmail.com wrote:
This string exists in native devenum and thus is subject to translation so I just have to find why regedit displays it badly when editing the registry. Wine traces functions also but I would it is more normal.
Hmm... odd indeed
I think regedit uses the ANSI codepage for the registry, while the translations are in UTF-8. I experienced this when importing .reg-files in UTF-8 with special characters in them.
The umlauts in the German translation of regedit's GUI however, are displayed correctly. Is your nbsp part of the GUI or a registry-key? I would guess the second.
Yes it's a registry-key. It's a prefix string in resource (which is thus subject to translation). I checked what I did and finally it seems to be displayed correctly in regedit. I think I confused myself. However in trace I get "DirectSound\00a0: default". The "A0" is there but nothing of "C2". Strange.
Christian
Le 13/03/2012 14:51, Frédéric Delanoy a écrit :
On Tue, Mar 13, 2012 at 11:52, Christian Costatitan.costa@gmail.com wrote:
Never heard of this rule for french or never paid attention but I'm fine with it if this is so.
Actually there should sometimes also be thin non-breakable spaces in po, but those are very badly supported, so are not used here.
Some links for your info: http://fr.wikipedia.org/wiki/Espace_typographique http://fr.wikipedia.org/wiki/Espace_ins%C3%A9cable (and other wikipedia pages) provide some information
This string exists in native devenum and thus is subject to translation so I just have to find why regedit displays it badly when editing the registry. Wine traces functions also but I would it is more normal.
Hmm... odd indeed
Frédéric
Thanks for the info. Finally regedit displays it well as I mention in another post.
Christian
On 13 March 2012 00:42, Christian Costa titan.costa@gmail.com wrote:
BTW, is there an editor that shows them ? gvim doesn't.
Assuming gvim is similar enough to normal vim, you can use listchars to highlight various things. Use nbsp for non-breaking spaces. You can use Ctrl+K to insert digraphs. Use "NS" for non-breaking space, :digraphs for a list.
On Tue, Mar 13, 2012 at 00:42, Christian Costa titan.costa@gmail.com wrote:
BTW, is there an editor that shows them ? gvim doesn't.
Emacs does.
Non-breakable space are only present in french translations. Between a name and a ':'.
Also after/before '«' and '»", as well as before "double" punctuation (;:?!).
This is not nicer to me. I wondering if that would not be better to remove them all...
It shouldn't be removed just because someone's editor doesn't show them. The said editor should be fixed instead, and not ignoring the typography rule.
Frédéric
Le 13/03/2012 14:40, Frédéric Delanoy a écrit :
On Tue, Mar 13, 2012 at 00:42, Christian Costatitan.costa@gmail.com wrote:
BTW, is there an editor that shows them ? gvim doesn't.
Emacs does.
Non-breakable space are only present in french translations. Between a name and a ':'.
Also after/before '«' and '»", as well as before "double" punctuation (;:?!).
This is not nicer to me. I wondering if that would not be better to remove them all...
It shouldn't be removed just because someone's editor doesn't show them. The said editor should be fixed instead, and not ignoring the typography rule.
Frédéric
I knew the rules for "!" and "?" but not for the others. The editor was not in cause. I just didn't know rule for ":" and was more used to them without space. I try emacs and indeed it shows a colored underscore. I will try configuring gvim.
Christian
On Mon, Mar 12, 2012 at 20:32, Christian Costa titan.costa@gmail.com wrote:
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for so the patch still applies.
Use a sane editor. Non-break space were explicitly added, as required by French typography.
Frédéric
-
Christian Costa -
Frédéric Delanoy -
Henri Verbeet -
Julian Rüger -
Michael Stefaniuc -
Nikolay Sivov