OpenOrienteering
OMAP file corruption from e-mail transfer
Based on a number of reports which I received via e-mail only.
OMAP files may have very long lines due to
- coordinate lists of long line objects.
- text paragraphs in descriptions
When sending OMAP files as e-mail attachments, some SMTP servers (or clients?) treat them as text and insert line breaks into very long lines (after app. 1000 bytes).
Actual behaviour
- Opening maps fails when a line break was inserted in a coordinate list.
- Translations of descriptions cannot be loaded when the source string was changed.
Expected behaviour
The app shall open the map without error.
- [x] There shall be no problem with handling line breaks in reading coordinates.
- [ ] There shall be some care to avoid, or a solution to handle, long text paragraphs.
Configuration
Mapper Version: v0.9.5 Operating System: all
There is a 998/1000 limit for characters in a line, but I assume that this of course should only be valid for the email's text body: https://datatracker.ietf.org/doc/html/rfc2822#section-2.1.1 Have the affected .omap files been transferred inline in an html email, i.e., does it make a difference whether emails are transmitted in plaintext oder html mode?
