osrm-backend/features
Daniel J. Hofmann bb244e28bb Adds a failing test case for 255 unicode code points
The OSM spec says "up to 255 full unicode chars", so we should be able
to handle 255 x 🐼 --- but we don't.

The internal limit is on 255 _bytes_ in the `std::string`, but there can
be up to four bytes in a utf8 encoded code point.

References:
- http://wiki.openstreetmap.org/wiki/API_v0.6#Tags
- http://www.fileformat.info/info/unicode/char/1f43c/browsertest.htm
- https://en.wikipedia.org/wiki/UTF-8#Description
2016-09-02 16:10:32 +02:00
..
bicycle basic turn lane handling 2016-06-27 10:07:41 +02:00
car ignore invalid only_* restrictions 2016-09-01 09:14:01 +02:00
foot Revert "Fixes roundabout spelling in existing cucumber test" 2016-06-02 15:00:49 +02:00
guidance improve segregated road detection 2016-08-24 10:34:07 +02:00
nearest Move nodes inside the search radius 2015-05-15 00:34:53 +02:00
options Fix exception handling around unrecognised options 2016-07-26 11:43:08 +02:00
raster Update raster features to reflect not cutting off arrive instruction 2016-04-05 22:59:14 +02:00
step_definitions We should be returning an error if any errors that occur during reprocessing. 2016-08-05 15:11:12 -07:00
stress cleanup indentation of cuke files 2013-08-29 19:29:13 +02:00
support Catch and report errors during osrm-contract tests. 2016-08-05 14:19:22 -07:00
testbot Adds a failing test case for 255 unicode code points 2016-09-02 16:10:32 +02:00