Line break outputting incorrect format about gettext-parser HOT 9 CLOSED

This is new behaviour since 5.0.0. But only when you set foldLength to 0, right?

from gettext-parser.

@smhg, I have not tried to mess with foldLength yet but this is a behavior since 4.2.0. I just upgraded to 5.0.0 and it's still the case. I will try foldLength and get back.

from gettext-parser.

Just tried const res = po.compile(out, {foldLength: 0}) and I get the same result

from gettext-parser.

@sinnstudio-nas I'm sorry, I mixed things up. This indeed has nothing to do with the recent changes (5.0.0).

Yes, line folding on newline characters seems to happen in any case.

Some thoughts:

• I think it would indeed be great to be able to configure line folding, as many different opinions seem to exists. And likely other options are necessary (as there are other characters on which folding happens).
• Maybe it is good to pull this into a separate library? With the foldLength option replaced by folding which will be passed on directly to the new library?

from gettext-parser.

@smhg so maybe a folding object that has properties like enabled and foldLength? That seems to be the better option here

from gettext-parser.

Yes, that's it I think. But putting a line-folding package on npm doesn't sound too bad I think?
It has little to do with gettext-conversion and others might use it. Also, it would separate the tests (as they neither have anything to do with gettext).
Do you feel like giving this a try?

from gettext-parser.

@smhg I would rather update the code here to account for all use cases for this project. Npm package may be a little heavy overtaking for me. Let me know your thoughts!

from gettext-parser.

That's ok if you can put the folding-related tests in a separate folder please.

from gettext-parser.

Solved with #67

from gettext-parser.