commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NET-365) FTPClient.listFiles() does not work properly, if remote server speaks German
Date Wed, 09 Mar 2011 11:33:00 GMT

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

Sebb commented on NET-365:
--------------------------

I agree it's a bug, but I think \D is too wide a match, as it matches space/tab etc.

Might be better to use \p{isL} (is Unicode letter), but there are possibly other solutions.

Is there a public ftp server we can use to test this against?

> FTPClient.listFiles() does not work properly, if remote server speaks German
> ----------------------------------------------------------------------------
>
>                 Key: NET-365
>                 URL: https://issues.apache.org/jira/browse/NET-365
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.2
>            Reporter: Johannes Katelaan
>
> If you are connecting to an FTP server that speaks German you will get German language
month names in result to a LIST command. For month names with three-letter abreviations that
are identical to the english versions (eg Jan) everything works fine. For month names that
are not identical to the englisch versions (eg Dez instead of Dec) you will get FTPFile entrys
without date/time information. This is just annoying, but OK.
> You get a real problem in March. The German abreviation is Mär, containing the German
umlaut character ä. File entries with a date in March will just be dropped without further
notice. I think this should be considered a bug.
> The reason for this behaviour is the REGEX in UnixFTPEntryParser, which matches only
to month names containing "normal" letters:
> {noformat}[a-zA-Z]{3}{noformat}
> So the month name "Mär" will not match.
> I fixed this by changing this part of REGEX to
> {noformat}\\D{3}{noformat}
> In REGEX there are two occurances of the not working part that have to be changed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message