Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Inconsistent footprint naming in C&K switches #759

Open
antoniovazquezblanco opened this issue Jul 18, 2018 · 7 comments
Open

Inconsistent footprint naming in C&K switches #759

antoniovazquezblanco opened this issue Jul 18, 2018 · 7 comments
Milestone

Comments

@antoniovazquezblanco
Copy link
Collaborator

Examples:
SW_SPST_CK_KSC6xxJLFx
SW_CuK_JS202011AQN_DPDT_Angled

What should we use for https://www.ckswitches.com/?

@antoniovazquezblanco antoniovazquezblanco changed the title Inconsisten footprint naming in C&K switches Inconsistent footprint naming in C&K switches Sep 18, 2018
@antoniovazquezblanco
Copy link
Collaborator Author

antoniovazquezblanco commented Sep 18, 2018

I know this is low-priority and targets v6 but if we define a naming convention, then we will be able to merge new additions without having to rename them in the future.

Alternatives:

@robkam
Copy link
Contributor

robkam commented Sep 18, 2018

It should be more generic than that. Leave out the manufacturer name and model. There are multiple brands and part names sharing the same footprints.

@antoniovazquezblanco
Copy link
Collaborator Author

Thank you for your input @robkam but unfortunatelly some of the footprints in the repository are manufacturer specific so we should anyways reach a consensus about how we name this manufacturer.

@poeschlr
Copy link
Collaborator

Can the ampersand sign be used in footprint names?

@antoniovazquezblanco
Copy link
Collaborator Author

antoniovazquezblanco commented Sep 18, 2018

According to http://kicad-pcb.org/libraries/klc/G1.1/ ampersand should not be used. Sorry I have not checked that before 🤦‍♂️ .

I would go with CK unless anyone proposes another alternative.

@poeschlr
Copy link
Collaborator

poeschlr commented Jan 1, 2019

I just tested it. & is ok for kicad. It is however maybe a different story for our footprint download page. (& would need to be escaped in urls)

@antoniovazquezblanco
Copy link
Collaborator Author

I would avoid using it. Footprint include that characters in filenames and could cause problems in some FS types. Given that the ampersand character is not accepted in G1.1 I would not use it. Just in case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants