Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3

Miklos Vajna <vmiklos -AT- frugalware.org>
Fri, 11 Feb 2011 18:04:00 +0100

On Fri, Feb 11, 2011 at 04:57:57PM +0000, Caolán McNamara <caolanm@redhat.com> wrote:

On Fri, 2011-02-11 at 17:35 +0100, Miklos Vajna wrote:

Hi,

This commit in master:

http://cgit.freedesktop.org/libreoffice/writer/commit/?id=a37fae128b4badc8f9f2201e28dca3e08948ddec

Fixes:

https://bugs.freedesktop.org/show_bug.cgi?id=33653

Could someone familiar with that code (Cedric, Caolan?) sign it off and
cherry-pick, please?


Done for 3-3, not for 3-3-1 though, that needs more acks.


Thanks.

In master the method now also has a sane name of
"DestFileFormatSupportsUnicode" or something like that.


Just SupportsUnicode(). :)

Attachment: pgpHpRxosZvSS.pgp
Description: PGP signature

Context

[Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Miklos Vajna
- Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Caolán McNamara
  - Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Miklos Vajna
  - Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Michael Meeks
- Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Cedric Bosdonnat
  - Re: [Libreoffice] [REVIEW] RTF unicode export - need patch review for -3-3 · Petr Mladek
  - Re: [Libreoffice] [REVIEW][PUSHED] RTF unicode export - need patch review for -3-3 · Petr Mladek

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.