
On Mon, Apr 6, 2009 at 3:28 PM, Toby Speight <T.M.Speight.90@cantab.net> wrote:
Clinton> 2. A hack in Element.java, which removes a space if it is the Clinton> second character of the highway name.
Perhaps the hack should be to remove spaces (or replace with no-break-space (U+0080) if that works) in 'ref' values when substituting? And the non-hack to write a filter action to do so? I could have a look at this if you like.
Since I probably won't have time to work on this until the weekend, I certainly have no objections if you or anyone looks at this and proposes something better than my ugly hack. ;-) Regarding the syntax for hex characters in the style file, I wonder if allowing arbitrary hex chars is an appropriate solution. - As far as I know, there are a limited number of known control characters which make sense for inserting into element names. - The codes for the same symbols vary depending on the 6 or 8 (or 10?) bit encoding for the label file. This would mean that different style files would have to be used depending on the encoding options used when invoking mkgmap. - Would it be more elegant to have something like ${motorway-symbol} in the style file, and coding to make the appropriate translations? Of course, if there are many more potential hex-codes that could be inserted, this approach would be nonsense. It would also be unnecessary if using the same style file for 6 and 8 bit encoding is an unrealistic use case. What do you think? Cheers.