A question about com.sun.star.frame.XStorable's URL
tabe at fixedpoint.jp
Mon Jan 23 10:26:32 UTC 2017
Thank you for your answer.
On Mon, 23 Jan 2017 10:10:45 +0100, Miklos Vajna <vmiklos at collabora.co.uk> wrote:
> On Fri, Jan 20, 2017 at 11:25:00AM +0900, Takeshi Abe <tabe at fixedpoint.jp> wrote:
>> Preparing a patch for tdf#105382 , I come across a question about
>> character encoding for the path part of a URL representing a
>> com.sun.star.frame.XStorable's location.
>> I wonder if the original (before percent-encoded) path of such a URL can
>> be in an encoding other than UTF-8 or even in a different charset due
>> to e.g. a code page of some legacy filesystems.
>> Is it possible?
>> And, if so, is there any reasonable way to tell the encoding?
> The UNO API works with UNOIDL strings, where those strings are
> represented as OUStrings in C++, which is an array of Unicode
> I think this means you have to decide encoding when you convert your
> OString (or other byte array) data to OUString, before calling any UNO
OK, that confirms my understanding about UNO API. But it still sounds
neutral whether the original path can be in a foreign encoding,
as the percent-encoded one can contain only ASCII chars (so may be passed
to UNO interface transparently.)
-- Takeshi Abe
More information about the LibreOffice