[@JazzyNico, comment #7]
The code in the trunk, 0.25 r204, is quite stable. It has enough code
additions to qualify as a 0.26 release IMO, but releases are up to
codedread to make.
Is "\r\n" on Windows satisfactory for you, or should Scour attempt to
really write "\n" everywhere? (reopening sys.stdout in binary mode, for
instance, with os.fdopen(sys.stdout.fileno(), "wb")) Windows Notepad
users will be happy with "\r\n", that's for sure :)
[@Jan Thor, original post and comment #8]
Great, that's good to hear. It didn't screw Inkscape to replace
os.linesep with "\n" everywhere after all, and standalone Scour works
well too.
[General]
The patch in comment #6 is now in the trunk as revision 204, but I'll
still wait for an answer to the above "\r\n" question.
** Changed in: scour
Importance: Undecided => Medium
** Changed in: scour
Status: Opinion => Fix Committed
** Changed in: scour
Assignee: (unassigned) => Louis Simard (louis-simard)
** Also affects: scour (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717826
Title:
Windows Newlines
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
