Attachment 18506 Details for Bug 17297 – trivial fix

[patch] trivial fix

constchars.patch (text/plain), 1.54 KB, created by Caolán McNamara on 2008-08-25 09:27:27 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Caolán McNamara

Created: 2008-08-25 09:27:27 UTC

Size: 1.54 KB

patch

obsolete

>diff -ru poppler-0.8.6.orig/poppler/UnicodeMap.cc poppler-0.8.6/poppler/UnicodeMap.cc
>--- poppler-0.8.6.orig/poppler/UnicodeMap.cc	2008-08-25 17:24:45.000000000 +0100
>+++ poppler-0.8.6/poppler/UnicodeMap.cc	2008-08-25 17:25:45.000000000 +0100
>@@ -121,7 +121,7 @@
> #endif
> }
> 
>-UnicodeMap::UnicodeMap(char *encodingNameA, GBool unicodeOutA,
>+UnicodeMap::UnicodeMap(const char *encodingNameA, GBool unicodeOutA,
> 		       UnicodeMapRange *rangesA, int lenA) {
>   encodingName = new GooString(encodingNameA);
>   unicodeOut = unicodeOutA;
>@@ -136,7 +136,7 @@
> #endif
> }
> 
>-UnicodeMap::UnicodeMap(char *encodingNameA, GBool unicodeOutA,
>+UnicodeMap::UnicodeMap(const char *encodingNameA, GBool unicodeOutA,
> 		       UnicodeMapFunc funcA) {
>   encodingName = new GooString(encodingNameA);
>   unicodeOut = unicodeOutA;
>diff -ru poppler-0.8.6.orig/poppler/UnicodeMap.h poppler-0.8.6/poppler/UnicodeMap.h
>--- poppler-0.8.6.orig/poppler/UnicodeMap.h	2008-08-25 17:24:45.000000000 +0100
>+++ poppler-0.8.6/poppler/UnicodeMap.h	2008-08-25 17:26:00.000000000 +0100
>@@ -52,12 +52,12 @@
>   static UnicodeMap *parse(GooString *encodingNameA);
> 
>   // Create a resident UnicodeMap.
>-  UnicodeMap(char *encodingNameA, GBool unicodeOutA,
>+  UnicodeMap(const char *encodingNameA, GBool unicodeOutA,
> 	     UnicodeMapRange *rangesA, int lenA);
> 
>   // Create a resident UnicodeMap that uses a function instead of a
>   // list of ranges.
>-  UnicodeMap(char *encodingNameA, GBool unicodeOutA,
>+  UnicodeMap(const char *encodingNameA, GBool unicodeOutA,
> 	     UnicodeMapFunc funcA);
> 
>   ~UnicodeMap();

Actions: View | Splinter Review

Attachments on bug 17297: 18506

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.