[
https://issues.apache.org/jira/browse/MIME4J-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615216#action_12615216
]
olegk edited comment on MIME4J-60 at 7/21/08 4:34 AM:
------------------------------------------------------------------
> What does the "int" returned by isLineDelimiter represent?
Please see javadocs. They are there for a reason.
> If I'm parsing "first line\r\nsecond line" wouldn't this result in B and E
> rules matching and so in a doubled newline?
No, if you skip CRLF entirely. This is the reason why the strategy returns an
int which can be used to differentiate one char and two char cases.
Oleg
was (Author: olegk):
> What does the "int" returned by isLineDelimiter represent?
Please see javadocs. There are there for a reason.
> If I'm parsing "first line\r\nsecond line" wouldn't this result in B and E
> rules matching and so in a doubled newline?
No, if you skip CRLF entirely. This is the reason why the strategy returns an
int which can be used to differentiate one char and two char cases.
Oleg
> Configurable strategy for line delimiters
> -----------------------------------------
>
> Key: MIME4J-60
> URL: https://issues.apache.org/jira/browse/MIME4J-60
> Project: Mime4j
> Issue Type: Wish
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.5
>
> Attachments: MIME4J-60-readLine-returns-no-newline.patch,
> newlinestrat.patch
>
>
> There is an ongoing discussion about how we should deal with non canonical
> line endings (isolated LF and/or isolated CR).
> This issue is to track discussion results and proposed patches.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
