[jira] [Updated] (SVN-1537) on win32, use wide-char functions for console i/o to reduce data loss

2016-11-08 Thread Gerard Agius (JIRA)

 [ 
https://issues.apache.org/jira/browse/SVN-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerard Agius updated SVN-1537:
--
Attachment: svn add failure.png

> on win32, use wide-char functions for console i/o to reduce data loss
> -
>
> Key: SVN-1537
> URL: https://issues.apache.org/jira/browse/SVN-1537
> Project: Subversion
>  Issue Type: Bug
>  Components: unknown
>Affects Versions: all
> Environment: Windows XP
>Reporter: Branko Čibej
>Priority: Critical
> Fix For: 1.9.0
>
> Attachments: 1537.png, 1_test_UnicodeInFilename.bat
>
>
> On NT-class variants of Windows, we should use the wide-character functions 
> for console I/O and use UTF-16 encoding. Using apr_app_initialize instead of 
> apr_initialize would also help, because command-line arguments and 
> environment strings would be made available in UTF-8, again avoiding the need 
> for lossy conversion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (SVN-1537) on win32, use wide-char functions for console i/o to reduce data loss

2016-11-08 Thread Gerard Agius (JIRA)

 [ 
https://issues.apache.org/jira/browse/SVN-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerard Agius updated SVN-1537:
--
Attachment: 1537.png

This appears to not be working?

svn 1.9.4
Windows 10.

> on win32, use wide-char functions for console i/o to reduce data loss
> -
>
> Key: SVN-1537
> URL: https://issues.apache.org/jira/browse/SVN-1537
> Project: Subversion
>  Issue Type: Bug
>  Components: unknown
>Affects Versions: all
> Environment: Windows XP
>Reporter: Branko Čibej
>Priority: Critical
> Fix For: 1.9.0
>
> Attachments: 1537.png, 1_test_UnicodeInFilename.bat
>
>
> On NT-class variants of Windows, we should use the wide-character functions 
> for console I/O and use UTF-16 encoding. Using apr_app_initialize instead of 
> apr_initialize would also help, because command-line arguments and 
> environment strings would be made available in UTF-8, again avoiding the need 
> for lossy conversion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)