{"shas":[["fa0768e9a8a1367fedcac74858fe3d08a89f8a71","10099878e72cf7e0ee4aa0cbce77aa8d5e6825f3@delorie.com","Add locale functions\n\nAdd textdomain() and setlocale() to connect to our message catalogs.","DJ Delorie"],["61bd0cb1e134bbea96abd6fd2d5fb94d09c0b3c8","1131b31988b060307ac241782243ebf25e705312@cam.ac.uk","Add another missing source file to POTFILES.in","Peter Clifton"],["a8b69632f0219923fdbc9df8c44abeed7356b495","10099878e72cf7e0ee4aa0cbce77aa8d5e6825f3@delorie.com","Wrap all XmStrings in gettext()","DJ Delorie"],["8147be7a70654c6c29d0e29e222c4014cf19fa5d","10099878e72cf7e0ee4aa0cbce77aa8d5e6825f3@delorie.com","Fix m4-to-newlib converter filenames\n\nThe m4 library uses macros and parameters to describe footprints, which\nallows for a *very* flexible footprint naming scheme.  While it is\nimpossible for pcb to know all valid footprint values, it does have a\nlist of \"standard\" ones, and knows how to obtain those.  However, the m4\nto newlib converter wasn't using the same footprint naming convention as\neveryone else, so produced *.fp files that weren't always useful.  For\nexample, there were a large number of 300.fp files that all collided.\n\nWith this fix, the footprint name matches the value in [...] in the\nlibrary window, which is what we tell people to use for the \"footprint=\"\nattribute anyway.","DJ Delorie"],["a2bcea72cf4161eb928582a28fac3443309d8050","10099878e72cf7e0ee4aa0cbce77aa8d5e6825f3@delorie.com","Add DIL footprint names and R025.\n\nExisting tutorials say to use \"DIL 16 300\" for DIPs (we use \"N 16 300\")\nand often call for the R025 footprint, so add them as aliases so the\nm4-to-newlib converter includes them.","DJ Delorie"]],"ref":"refs/heads/master","size":5,"head":"a2bcea72cf4161eb928582a28fac3443309d8050","push_id":42985750}