5.3     Safe Utility function to prepend '0' characters to a string representing a number. This allows you to ensure a fixed width for numbers that are less than the desired width in size. This comes up frequently when representing numbers in other bases greater than 10 as they are inevitably presented as text, and not having them evenly justified can (at best) be ugly and (at worst) actually lead to parsing and conversion bugs.FTake an arbitrary string, hash it, then pad it with zeros up to be a digits-long string in base 62.You may be interested to know that the 160-bit SHA1 hash used here can be expressed without loss as 27 digits of base 62, for example:#hashStringToBase62 27 "Hello World"1T8Sj4C5jVU6iQXCwCwJEPSWX6uSafeV1c8A symbol set with sixteen uniquely pronounceable digits.ZThe fact there are sixteen symbols is more an indication of a certain degree of bullheaded-ness on the part of the author, and less of any kind of actual requirement. We might have a slighly better readback score if we dropped to 15 or 14 unique characters. It does mean you can match up with hexidecimal, which is not entirely without merit.KThe grouping of letters and numbers was the hard part; having come up with the set and deconflicted the choices, the ordering is then entirely arbitrary. Since there are some numbers, might as well have them at the same place they correspond to in base 10; the letters were then allocated in alpha order in the remaining slots.'0' 0th '1' 1st '2' 2nd 'C' 3rd '4' 4th 'F' 5th'H' 6th'7' 7th'8' 8th'9' 9th'K' 10th'L' 11th'M' 12th'R' 13th'X' 14th'Y' 15th:Given a number, convert it to a string in the Locator16 base 16 symbol alphabet. You can use this as a replacement for the standard '0'-'9' 'A'-'F' symbols traditionally used to express hexidemimal, though really the fact that we came up with 16 total unique symbols was a nice co-incidence, not a requirement.Represent a number in Locator16a format. This uses the Locator16 symbol set, and additionally specifies that no symbol can be repeated. The a in Locator16a represents that this transformation is done on the cheap; when converting if we end up with '9' '9' we simply pick the subsequent digit in the enum, in this case getting you '9' 'K'. Note that the transformation is not reversible. A number like 4369 (which is 0x1111, incidentally) encodes as 12C4. So do 4370, 4371, and 4372. The point is not uniqueness, but readibility in adverse conditions. So while you can count locators, they don't map continuously to base10 integers.The first argument is the number of digits you'd like in the locator; if the number passed in is less than 16^limit, then the result will be padded.toLocator16a 6 436912C40FCGiven a number encoded in Locator16, convert it back to an integer.PTake an arbitrary sequence of bytes, hash it with SHA1, then format as a short digits-long Locator16 string.&hashStringToLocator16a 6 "Hello World"M48HR0    Andrew Cowie ExperimentalSafe2         &locators-0.2.4.4-ARSNoxMqJJUX1Kd4qrXg8 Data.LocatorData.Locator.HashesData.Locator.LocatorstoBase62 padWithZeros fromBase62hashStringToBase62LocatorlocatorToDigitdigitToLocator English16ZeroOneTwoCharlieFourFoxtrotHotelSevenEightNineKiloLimaMikeRomeoXRayYankee toLocator16 toLocator16a fromLocator16hashStringToLocator16a