[ 
https://issues.apache.org/jira/browse/NET-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906991#comment-13906991
 ] 

Sebb edited comment on NET-516 at 2/20/14 2:19 PM:
---------------------------------------------------

bq. Apache ORO uses perl flavored regex in which .(dot) metacharacter matches 
any character except \n

Thanks! This suggests another possible approach which is to use the following RE

{noformat}
(\\S[^\\n]*)
{noformat}

That would be closest to the ORO original.
However it means changing all the REs, and is not necessarily better than using 
DOTALL in the shared parent implementation.


was (Author: [email protected]):
bq. Apache ORO uses perl flavored regex in which .(dot) metacharacter matches 
any character except \n

Thanks! This suggests another possible approach which is to use the following RE

{format}
(\\S[^\\n]*)
{format}

That would be closest to the ORO original.
However it means changing all the REs, and is not necessarily better than using 
DOTALL in the shared parent implementation.

> parser problem occurs if the filename contains one or more characters of 
> which the second byte of Shift-JIS code is 0x85
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NET-516
>                 URL: https://issues.apache.org/jira/browse/NET-516
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: windows
>            Reporter: Asha K S
>             Fix For: 2.0
>
>         Attachments: FTPSample.java, notworking.png, working.png
>
>
> Problem occurs if the filename contains one or more characters of which the 
> second byte of Shift-JIS code is 0x85, on a windows Japanese machine when 
> listing file names from IIS FTP server.
> This was working fine in commons-net-1.4.0.jar . 
> [This relates to the NTFTPEntryParser]



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to