Put all keys in consistent order and remove/fix bogus mime types, some
assigned to programs that don't even open files. Those files could use
some TLC from translators to provide translated names and tooltips, I
preserved some of the french that was already in the files.
Quick and dirty script gathers the original SVG icons from the
bitmaps_png folder and generates bitmaps at several sizes named
according to the mime type or application name. To get the names, the
script reads the kicad-kicad.xml mime package and the application
.desktop files, reconciling both to make sure all defined types have
proper associations.
This renames (well, actually regenerates from the originals) all the
icons installed on Linux to match the correct mime type names, and
adds all the missing icons in some sizes.
This file registers the file extensions used by kicad and their
corresponding mimetypes. Before this change the file was refering to
the old .brd extension and the wrong mime type. The file was also
renamed to kicad-kicad.xml to conform to the XDG spec which expects a
vendor-product pair as the package name.
Commit BZR 6703 introduced a minor horizontal adjustment for stroke
text rendering in GAL, but the Translate() call was done before
calling Save(). So, when this function was called multiple times a
residual offset carried over to each subsequent line.
bzr 6703 = git 67982a4
This makes sure that the declaration is always the same within a single
module, so all users have the same idea of whether the symbol is imported.
In all dynamically linked objects, all users should be aware that the
symbol is imported, while in the statically linked bitmap2component
program, no import/export decorations should be used.
This function has two conflicting definitions in the "kicad" executable and
the other wrapper programs. As the kifaces can be loaded from either, this
silently assumes compatible data layout for the PGM_KICAD and PGM_BASE
types when passed by reference, which is valid only when the compiler is
aware of the cast.
If the return type is encoded in the symbol name (such as when using the
MSVC compiler), this also causes an error during linking, as the symbol
names no longer match.
While defining functions in another namespace is technically allowed as
long as the definition can be matched to a declaration, this can lead to
ambiguous resolutions, such as here (GAL vs KIGFX).