On Wed, 29 Dec 2010, Alan Mintz wrote:
The workarounds have been removed some months ago. There should be nothing
left. If there is, tell where and file a bug-report.
I don't really understand what that means. I am saying there are different
separators visibly present, with different logical
At 2010-12-29 07:18, =?ISO-8859-15?Q?Dirk_St=F6cker?= wrote:
On Wed, 29 Dec 2010, Alan Mintz wrote:
Yes. I used 0x1E (and yes, I know my standards), as semicolon had lots
of troubles, same with comma and everthing else. E.G. the commit
comments use all of these characters. Previously it has be
On Wed, 29 Dec 2010, Frederik Ramm wrote:
I don't know how to enter it by hand. I always used copy&paste :-)
When I use the standard way of copy+paste under X - mouse select, then middle
mouse button, no key presses - this results in a double ^ and not the desired
0x1e. In fact even fumblin
On Wed, 29 Dec 2010, Alan Mintz wrote:
Yes. I used 0x1E (and yes, I know my standards), as semicolon had lots of
troubles, same with comma and everthing else. E.G. the commit comments use
all of these characters. Previously it has been ';' as well as ',' and some
forms of §.
I don't mind whi
Hi,
On 12/29/10 14:34, Dirk Stöcker wrote:
I don't know how to enter it by hand. I always used copy&paste :-)
When I use the standard way of copy+paste under X - mouse select, then
middle mouse button, no key presses - this results in a double ^ and not
the desired 0x1e. In fact even fumblin
At 2010-12-29 04:25, =?ISO-8859-15?Q?Dirk_St=F6cker?= wrote:
On Wed, 29 Dec 2010, Frederik Ramm wrote:
I am slightly unhappy about the fact that we have control characters
(more specifically, the "record separator" 0x1e ...
Yes. I used 0x1E (and yes, I know my standards), as semicolon had l
On Wed, 29 Dec 2010, Frederik Ramm wrote:
Why did you not go with a semicolon and escape it when it occurred elsewhere?
Given that 0x1E is a valid character that might conceivably appear inside a
value, you must have some sort of escaping rule anyway - why not apply the
same escaping rule but
Hi,
On 12/29/10 13:25, Dirk Stöcker wrote:
Yes. I used 0x1E (and yes, I know my standards), as semicolon had lots
of troubles, same with comma and everthing else. E.G. the commit
comments use all of these characters. Previously it has been ';' as well
as ',' and some forms of §.
Why did you no
On Wed, 29 Dec 2010, Frederik Ramm wrote:
I am slightly unhappy about the fact that we have control characters (more
specifically, the "record separator" 0x1e - someone must really have read
their standards) in the config file. This means that I cannot simply email
someone and say "add this
JOSM devs,
I am slightly unhappy about the fact that we have control characters
(more specifically, the "record separator" 0x1e - someone must really
have read their standards) in the config file. This means that I cannot
simply email someone and say "add this line to your config file" (e.g
10 matches
Mail list logo
