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.

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

indicators not interpreting CarriageReturn/LineFeed on load #6

Open
Neon22 opened this issue Jan 18, 2020 · 1 comment
Open

indicators not interpreting CarriageReturn/LineFeed on load #6

Neon22 opened this issue Jan 18, 2020 · 1 comment

Comments

@Neon22
Copy link

Neon22 commented Jan 18, 2020

If an indicator is saved with a CarriageReturn/LineFeed embedded in it appears like this in the .pattern xml file:

<indicator>
            <x>115.608</x>
            <y>-98.4189</y>
            <text>3. Pickup prior loop again.
    sc through next stitch.</text>

However on reload the carriage return is being ignored on reading and the indicator shows as a single line of text.

Note the character at the end of the line is a LineFeed. This is the same as every other line. so no CarriageReturn is actually in file.

Not sure if correct solution is in encoding to file, or in reading from file.

@Neon22
Copy link
Author

Neon22 commented Jan 18, 2020

Its worth noting that IF the .pattern and .set files could be forced into ASCII XML then:

  • external editing/generation of files would be easier,
  • transferring files between people would be easier because they could be cut and pasted. At the moment a binary transfer mechanism is essential and difficult.

For example, no forum swaps are possible.

Its also probable that forcing ASCII XML could eliminate a number of other problems (e.g. multi-line notifications).

@Neon22 Neon22 changed the title indicators not interpreting <cr> on load indicators not interpreting CarriageReturn/LineFeed on load Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant