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

Gunther Wiest edited comment on JCLOUDS-1423 at 11/9/18 2:21 PM:
-----------------------------------------------------------------

I'm not confident with the ProcessBuilder, and how to set or retrieve the used 
codepages. I think a solution would be, if there is a possibility to set the 
codepage of the output of the process, or to retrieve the used codepage of the 
output of the process, and use this retrieved Codepage to initialize the 
InputStreamReader via
{code:java}
public InputStreamReader(InputStream in, String charsetName){code}
I spent some time looking for a solution, but I didn't succed.


was (Author: wigu):
I'm not confident with ProcessBuilder, and how to set or retrieve the used 
codepages. I think a solution would be, if there is a possibility to set the 
codepage of the output of the process, or to retrieve the used codepage of the 
output of the process, and use this retrieved Codepage to initialize the 
InputStreamReader via
{code:java}
public InputStreamReader(InputStream in, String charsetName){code}
I spent some time looking for a solution, but I didn't succed.

> BlobStore.putBlob throws RuntimeException with filesystem provider on RUSSIAN 
> localized Windows
> -----------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1423
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1423
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 2.0.2
>         Environment: Microsoft Windows (tested on 7 and 10), Java 7 and 8.
>            Reporter: Gunther Wiest
>            Priority: Minor
>              Labels: filesystem, windows
>             Fix For: 2.1.0, 2.0.1
>
>
> When using the filesystem provider on a localized RUSSIAN Windows system 
> putBlob consistenly throws a RuntimeException. The put operation does 
> succeed, however, meaning a viable workaround is to catch-and-ignore.
> The cause of the Exception is a UserPrincipalNotFoundException which is 
> thrown in org.jclouds.filesystem.util.Utils while trying to resolve the 
> Windows SID 'S-1-1-0' user group using 
> UserPrincipalLookupService.lookupPrincipalByName.
>  
> The Russian translation for everyone is "Все", and the output of the "whoami" 
> command will be in [https://de.wikipedia.org/wiki/Codepage_866] wich turns 
> into different characters, when read into a java string via 
> "ProcessBuilder.start". This is the reason why the "lookupPrincipalByName" 
> fails.
> This will occur on all windows systems, where the translation contains non 
> standard ASCII 7 bit characters. See also  
> [https://www.microsoft.com/en-us/language/Search?&searchTerm=Everyone&langID=Russian&Source=true&productid=All%20Products]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to