Attachment 120 Details for Bug 268 – Fixes the issues

[patch] Fixes the issues

xdgmime_utf8.patch (text/plain), 1.51 KB, created by Alexander Larsson on 2004-03-04 02:29:26 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alexander Larsson

Created: 2004-03-04 02:29:26 UTC

Size: 1.51 KB

patch

obsolete

>Index: xdgmimeint.c
>===================================================================
>RCS file: /cvs/gnome/gnome-vfs/libgnomevfs/xdgmimeint.c,v
>retrieving revision 1.3
>diff -u -p -r1.3 xdgmimeint.c
>--- xdgmimeint.c	20 Jan 2004 20:02:33 -0000	1.3
>+++ xdgmimeint.c	4 Mar 2004 10:28:19 -0000
>@@ -37,7 +37,7 @@
> #define	TRUE	(!FALSE)
> #endif
> 
>-const unsigned char _xdg_utf8_skip_data[256] = {
>+static const unsigned char _xdg_utf8_skip_data[256] = {
>   1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
>   1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
>   1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
>@@ -51,7 +51,6 @@ const unsigned char _xdg_utf8_skip_data[
> const char * const _xdg_utf8_skip = _xdg_utf8_skip_data;
> 
> 
>-
> /* Returns the number of unprocessed characters. */
> xdg_unichar_t
> _xdg_utf8_to_ucs4(const char *source)
>Index: xdgmimeint.h
>===================================================================
>RCS file: /cvs/gnome/gnome-vfs/libgnomevfs/xdgmimeint.h,v
>retrieving revision 1.3
>diff -u -p -r1.3 xdgmimeint.h
>--- xdgmimeint.h	20 Jan 2004 20:02:33 -0000	1.3
>+++ xdgmimeint.h	4 Mar 2004 10:28:19 -0000
>@@ -52,7 +52,7 @@ typedef unsigned int   xdg_uint32_t;
> 					      (((xdg_uint32_t)(val) & 0x000000FFU) << 24))
> /* UTF-8 utils
>  */
>-const char *const _xdg_utf8_skip;
>+extern const char *const _xdg_utf8_skip;
> #define _xdg_utf8_next_char(p) (char *)((p) + _xdg_utf8_skip[*(unsigned char *)(p)])
> #define _xdg_utf8_char_size(p) (int) (_xdg_utf8_skip[*(unsigned char *)(p)])
>

Actions: View | Splinter Review

Attachments on bug 268: 120

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.