kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

Hi Evan,

The code prohibits the following in filenames:

\/:"<>|

Note that the prohibited list does not include spaces.  (In theory all the escaping bugs are now fixed.)

Netnames (and therefore pin names and labels) don’t have filename constraints, so you can in theory use anything that’s not a control character (<tab>, <return>, etc.).  However, we use [] and {} for bus definitions, so best to stay away from them in netnames.

I don’t know of any regression tests for this, but I never got the testing framework running on my Mac so I’m not terribly familiar with it.

Cheers,
Jeff.


> On 6 Sep 2019, at 18:29, Evan Shultz <evan.shultz@xxxxxxxxx> wrote:
> 
> Hi all,
> 
> http://kicad-pcb.org/libraries/klc/G1.1/ <http://kicad-pcb.org/libraries/klc/G1.1/> shows a limited set of characters that can be used in the official library. https://github.com/KiCad/kicad-symbols/pull/2090 <https://github.com/KiCad/kicad-symbols/pull/2090> sparked a conversation about allowing other characters, and as one of the librarians I want to solicit dev input.
> 
> 1. Can anyone comment on the list of accepted chars in KLC? Is that correct as of now? Are there other characters that can be allowed?
> 2. Is regression testing done to check acceptable characters over all supported OSes for KiCad? Ultimately my question is that if were to be code changes that impact the set of characters KiCad should handle, is there a way to be alerted to a problem before a version of KiCad would be released?
> 
> Thanks!
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp