kicad-developers team mailing list archive

[Marco Ciampa <ciampix@xxxxxxxxx>]

On Wed, Oct 08, 2014 at 11:38:34AM +0200, Benoît Roehr wrote:
> Hello dear developers.
> 
> Le 08/10/2014 10:08, Andrew Zonenberg a écrit :
> >Second the vote for consistency, no matter which way it goes.
> >
> >Personally, I have a slight preference for "footprint" over "module" as
> >well.
> >
> >On Wed, 2014-10-08 at 18:56 +1100, Mitch Davis wrote:
> >>On Wed, Oct 8, 2014 at 5:47 PM, Mark Roszko <mark.roszko@xxxxxxxxx> wrote:
> >>>Hehe, well, I guess everything can be renamed in the opposite
> >>>direction. But consistency is needed.
> >>YES PLEASE!  A number of people I've spoken to were really confused by
> >>this inconsistency.
> >>
> >>I use footprint myself.  Though footprint seems to imply what a PCB
> >>must have in order to accommodate a part, eg, pads, silk.  Are the 3d
> >>models part of this?  If they are, then footprint might not be the
> >>best term.
> I agree with this. What you want to rename "Footprint" is more or
> less a container unifying different PCB objects (pads, lines, 3d
> model...), but may not be a footprint (logos, mounting holes,
> screws...)
> 
> Altium folks use the "Component" term both in Schematic libraries
> and PCB libraries. You know what you are looking at knowing what
> type of library is browsed. I don't remember for Proteus.

These are my quick thoughts and I hope they make sense:

1) I personally have taken the freedom to translate footprint / footprint
module / module in Italian as "modulo" for module. I think that the best
name in English is module and all occurrences should be converted into
module for consistency.

2) I think that it is better to have "component" for schema and "module"
for pcb so there is no confusion when talking about component - module
association.

3) I think that translations should be put inside of the main source
tree. If someone wants to keep translations into a separate package it is
simple to do it anyway. Take a look at other programs: documentation is
usually kept separate but translations are always part of the program.

Why do I think this is important? Because translators usually play a big
part in clearing reference source strings from small errors, typos and
inconsistency because they have to read all strings together and thus are
in the best position to detect errors and typos. Those small errors
usually are left unchanged because it seems always not worth the patch or
the burden to disturb a dev to apply the fix.

bye

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

+--------------------+
| Linux User  #78271 |
| FSFE fellow   #364 |
+--------------------+