You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When initialising the Unicode filter, the user should have the ability to specify which line endings to use:
# Unix line endings (default)>>>f.Unicode(convert_newlines='\n').apply('Foo\nBar\rBaz\r\n')
'Foo\nBar\nBaz\n'# Windows line endings>>>f.Unicode(convert_newlines='\r\n').apply('Foo\nBar\rBaz\r\n')
'Foo\r\nBar\r\nBaz\r\n'# Custom line endings>>>f.Unicode(convert_newlines='|').apply('Foo\nBar\rBaz\r\n')
'Foo|Bar|Baz'# Line endings unmodified>>>f.Unicode(convert_newlines=False).apply('Foo\nBar\rBaz\r\n')
'Foo\nBar\rBaz\r\n'
Note that this change potentially conflicts with the normalize argument, so we'll probably need to make a couple of additional changes to support this new functionality:
Add a remove_unprintables argument.
Rename normalize to normalize_unicode.
Deprecate the normalize argument.
The text was updated successfully, but these errors were encountered:
Might make more sense to create 3 new filters (StripUnprintables, NormalizeUnicode, ConvertNewlines), and then convert the Unicode filter into a macro. Just sayin'... 😸
When initialising the
Unicode
filter, the user should have the ability to specify which line endings to use:Note that this change potentially conflicts with the
normalize
argument, so we'll probably need to make a couple of additional changes to support this new functionality:remove_unprintables
argument.normalize
tonormalize_unicode
.normalize
argument.The text was updated successfully, but these errors were encountered: