Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Wayne Stambaugh
It probably doesn't make much sense at this point given that the file format is going to be replaced in v6 so it will be a moot issue. I plan on quoting all strings in the new file format so spaces will pose no problem. On 02/16/2018 06:57 PM, hauptmech wrote: > Just adding another opinion to

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread hauptmech
Just adding another opinion to the mix here. %20 does not make the current file format any more difficult to read than it already is. The current format can be parsed by a human and edited with a text editor. That's good, and that's all you need. \x20 (which is what you would use if you were

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Jeff Young
> My beef with % encoding is that it is not human readable. I won’t argue with that. It’s a struggle at best. > On 16 Feb 2018, at 21:17, Wayne Stambaugh wrote: > > My beef with % encoding is that it is not human readable. Human > readability is an important goal when

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Wayne Stambaugh
My beef with % encoding is that it is not human readable. Human readability is an important goal when designing KiCad file formats. On 2/16/2018 4:04 PM, Jeff Young wrote: > Yeah, that’s why I was suggesting %-encoding. Substituting %20 for spaces > wouldn’t be a file format change. And it’s

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Jeff Young
Yeah, that’s why I was suggesting %-encoding. Substituting %20 for spaces wouldn’t be a file format change. And it’s a common enough escape sequence that anyone writing 3rd-party tools could easily deal with it. I think %-encoding is probably better than ‘\’-prefixing, mostly because it can

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Wayne Stambaugh
The space issue is tricky because it's not a quoted string. Quoting the string would be a file format change although you could make the argument so is the space. I believe all of the other strings in question are quoted in the file format so it should just be a matter of quoting any special

Re: [Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Seth Hillbrand
Hi Jeff- I was working on that but just got slammed at work, so there's been less time for testing/fixing all of the places where it touches. But there's a three-day weekend coming up here in the states, so I'm hopeful (eternally so) that there will be sufficient time to complete it. That said,

[Kicad-developers] Reverse parsing for spaces

2018-02-16 Thread Jeff Young
There was an issue a while back where we were considering reverse parsing something or another so that spaces didn’t trip us up. What’s the status of that? The reason I ask is that I’m looking at another bug where a user wants to put ‘/‘ characters in their global labels (which we of course