search

KiCad / kicad-library

The schematic and 3D libraries for KiCad 4.0. Note that the footprint libraries are the *.pretty repos themselves. This is an orphaned repo, the news about the v5 libs, http://kicad.org/post/kicad-official-libraries/.
Other
746 stars 956 forks source link

Slash in symbol names - violation of the new KLC? #1799

Closed ghost closed 6 years ago

ghost commented 6 years ago

Hi there,

i have a question regarding the naming of symbols.

For example, there is a PIC microcontroller named "PIC10(L)F320-I/MC".

But when i check the lib with the kicad-library-utils, it says that the slash between I an MC is a violation of the KLC.

Should i change the name of the symbol?

Best regards,

lavadew.

SchrodingersGat commented 6 years ago

The ( and ) characters are also violations!

These symbols predate the new requirements, which is why they are still in the library.

In short, yes if you are submitting new symbols they must not have these characters.

e.g.

bobc commented 6 years ago

I did a grep and there are quite a few :)

I think the "LF" variants should be an alias.

adc-dac.lib:DEF MCP3425A0T-E/CH U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP3550-50-E/MS U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP3550-60-E/SN U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP4801-E/MC U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP4901-E/MC U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP4921-E/MS U 0 40 Y Y 1 F N
adc-dac.lib:DEF MCP4922-E/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10(L)F320-I/MC U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10(L)F320-I/OT U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10(L)F320-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F200-I/MC U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F200-I/OT U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F200-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F204-I/MC U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F204-I/OT U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F204-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F220-I/MC U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F220-I/OT U 0 40 Y Y 1 F N
MCU_Microchip_PIC10.lib:DEF PIC10F220-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12(L)F1501-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12(L)F1822-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12(L)F1840-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C508-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C508A-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C509-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C509A-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C671-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12C672-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12CE518-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12CE519-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12CE673-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12CE674-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12CR509A-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F508-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F509-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F510-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F519-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F609-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F615-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F617-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F629-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F635-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F675-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F683-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12F752-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12HV609-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12HV615-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12HV752-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC12.lib:DEF PIC12LF1840T48-I/ST U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1454-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1454-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1455-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1455-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1459-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1459-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1503-I/MG U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1503-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1507-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1507-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1508-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1508-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1509-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1509-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1512-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1512-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1513-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1513-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1516-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1516-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1517-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1517-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1517-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1518-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1518-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1519-I/MV U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1519-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1519-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1526-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1527-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1829-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1829-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1934-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F1934-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F610-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F610-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F616-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F616-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627-xxI/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627-xxI/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627-xxI/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627A-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627A-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F627A-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F684-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F684-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F73-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F73-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F73-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F73-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F74-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F818-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F818-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F818-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F818-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F870-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F870-I/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F870-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F871-I/L U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F871-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F871-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F873-XXI/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F873-XXI/SP U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F874-XXI/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F874A-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F874A-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F88-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F88-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16(L)F884-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F1829LIN-E/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F505-I/MG U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F505-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F505-I/SL U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F505-I/ST U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F54-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F54-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F54-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F631-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F631-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F631-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F677-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F677-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F677-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F685-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F685-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F685-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F687-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F687-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F687-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F690-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F690-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F690-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F716-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F716-I/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F716-I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F83-XX/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F83-XX/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F84A-XX/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F84A-XX/SO U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F84A-XX/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC16.lib:DEF PIC16F882-I/P U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F13K50-E/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F13K50-E/SO U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F13K50-E/SS U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2331-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2331-I/SO U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2331-I/SP U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F23K20_I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2450-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2450-I/SO U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2450-I/SP U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2455-I/SO U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F2455-I/SP U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F25K80_I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F25K80_I/SS U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4331-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4331-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4331-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F442-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F442-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4450-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4450-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4450-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4455-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4455-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4455-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4458-I/ML U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4458-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4458-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F448-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F44J10-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F4580-I/P U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F45K80-I/ML U 0 40 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F45K80-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F66J60-I/PT U 0 50 Y Y 1 F N
MCU_Microchip_PIC18.lib:DEF PIC18F96J60-I/PT U 0 20 Y Y 1 F N
MCU_Microchip_PIC24.lib:DEF PIC24FV32KA304-I/PT IC 0 40 Y Y 1 F N
MCU_Microchip_PIC32.lib:DEF PIC32MX1XXFXXXD-I/PT U 0 40 Y Y 1 F N
MCU_Microchip_PIC32.lib:DEF PIC32MX2XXFXXXD-I/PT U 0 40 Y Y 1 F N
microchip.lib:DEF MCP2050-330-E/MQ U 0 40 Y Y 1 F N
microchip.lib:DEF MCP2050-330-E/P U 0 40 Y Y 1 F N
microchip.lib:DEF MCP2050-330-E/SL U 0 40 Y Y 1 F N
microchip.lib:DEF MCP2515-E/ST U 0 40 Y Y 1 F N
motorola.lib:DEF MCF5328/BGA256 U 0 40 Y Y 1 F N
sensors.lib:DEF MCP9700AT-E/LT U 0 40 Y Y 1 F N
sensors.lib:DEF MCP9700T-H/TT U 0 40 Y Y 1 F N
xilinx.lib:DEF XC3S1400A/FG484 U 0 40 Y Y 2 L N
xilinx.lib:DEF XC3S200AN/FT256 U 0 40 Y Y 1 F N
xilinx.lib:DEF XC3S50AN/TQG144 U 0 40 Y Y 1 F N
ghost commented 6 years ago

okay, we have quite a bunch to change. thanks for the info, issue can be closed.

SchrodingersGat commented 6 years ago

If you have the time, a fix for this would be greatly appreciated :)

ghost commented 6 years ago

yeah, will tackle this.

poeschlr commented 6 years ago

I would say we don't close this until the pull request is created.

bobc commented 6 years ago

I think we can leave open, it is a useful placeholder. I used the one line egrep "^DEF" *.lib | egrep -v "DEF [~]*[A-Za-z0-9-_\.]+ " >t.txt

This found some parts using "+", including many power symbols of course e.g. "+5V" - should "+" also be allowed in name?

In addition to parts using "/":


device.lib:DEF D_Bridge_+-AA D 0 50 Y Y 1 F N
device.lib:DEF D_Bridge_+A-A D 0 50 Y Y 1 F N
device.lib:DEF D_Bridge_+AA- D 0 50 Y Y 1 F N
device.lib:DEF D_Bridge_-A+A D 0 50 Y Y 1 F N
device.lib:DEF D_Bridge_-AA+ D 0 50 Y Y 1 F N
maxim.lib:DEF DS1307+ U 0 30 Y Y 1 F N
maxim.lib:DEF MAX7325AEG+ U 0 40 Y Y 1 F N
motor_drivers.lib:DEF L298(H)N U 0 40 Y Y 1 F N
SchrodingersGat commented 6 years ago

@bobc good point regarding the + character, had not thought of this one. We definitely need to allow that.

ghost commented 6 years ago
ghost commented 6 years ago

question for the Microchip MCUs: Everyone agrees, that the LF variants should be aliases?

SchrodingersGat commented 6 years ago

Yes using aliases is a sensible approach.

hildogjr commented 6 years ago

Yes, I had the problem with the MCP4922-E/P too. This problem just appear in the 10/Nov/2017 update (maybe because the new table library in Eeschema). To turn around I create my on symbol "MCP4922-E_P" copying the internal part in the library to may personal library.

tr-soft commented 6 years ago

I'm sorry, but can I found somewehere why you choose to disallow slash in part names? I'm software developer too, but I can't imagine that I make a decision where I disallow naming parts in form in which manufacturer labels them. It doesn't make any sense that developers of software to aid create schematic "dictate" me that I've to name parts differentially.

poeschlr commented 6 years ago

Well first off all the symbol/footprint names are used as file names. (for symbols this will happen shortly as soon as the new file format is published.) "/" in filenames is a bad idea because this char is use as path separator.

And it seems that the current implementation of the new symbol lib table already assumes there is no such char in the names.

tr-soft commented 6 years ago

Ok, I see the parallel with filenames but this is developer's decision that component have to have same name as filename and component name is "duplicated" in file content. Other tools doesn't have this constraint, I think this is as same as if OS developers says that 'red' color will not be supported in new version. In the market there are many many parts that have slash in label, so why make decision that this wouldn't be possible.

poeschlr commented 6 years ago

Ask over at the mailing list ;)

bobc commented 6 years ago

The decision to store data in separate files was made a while ago, personally I would not have done it that way, but I don't have influence on the developers. Even so, the file name could be suitably encoded to ensure that a valid file name is created - cf encoding of HTTP urls. The file name might lose a little readability if special chars are used, but not much.

Regardless, any scheme different to the current one requires someone to write some code, and that doesn't happen by magic. You could either discuss with the developers and submit a patch, or raise an issue on the bug tracker and hope that one day a developer shares your point of view and is motivated to improve KiCad.

SchrodingersGat commented 6 years ago

I am closing this issue as all the illegal characters have been fixed in the new symbol library