Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should GeoDesk remove CR/LF from strings? #94

Closed
clarisma opened this issue Feb 12, 2023 · 1 comment
Closed

Should GeoDesk remove CR/LF from strings? #94

clarisma opened this issue Feb 12, 2023 · 1 comment
Labels
clarify Spec is unclear about behavior

Comments

@clarisma
Copy link
Owner

The current spec requires any character below 32 (unprintable characters) in all OSM strings to be replaced with space.
Are there use cases where characters like CR/LF should be preserved? (Used mostly for longer text, such as inscriptions on memorials)
@clarisma clarisma added the clarify Spec is unclear about behavior label Feb 12, 2023
@clarisma clarisma mentioned this issue Feb 12, 2023
Closed
@clarisma
Copy link
Owner Author

Spec for 2.0 requires all tag values to be preserved.
Formatters must escape all whitespace/unprintable characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarify Spec is unclear about behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clarisma