From: taeyoon <taeyoon0.lee@samsung.com>
Date: Tue, 9 Aug 2016 11:27:47 +0000 (+0900)
Subject: Revert "[3.0] Change 'char' type to 'signed char'"
X-Git-Tag: accepted/tizen/common/20160830.150353~35
X-Git-Url: http://review.tizen.org/git/?p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git;a=commitdiff_plain;h=224d029462ff76be35979a454b8008becd1b5d21

Revert "[3.0] Change 'char' type to 'signed char'"

This reverts commit ed648574f04ce428c45474b3ed86076e2e222ebf.

Change-Id: I4cf7dce38ecaddc12da3aa0b4bb900acf6ce32b9
---

diff --git a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
index a6c843e..a3f3bdb 100644
--- a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
+++ b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
@@ -878,11 +878,12 @@ static void nsvg__fillScanline(unsigned char* scanline, int len, int x0, int x1,
 // note: this routine clips fills that extend off the edges... ideally this
 // wouldn't happen, but it could happen if the truetype glyph bounding boxes
 // are wrong, or if the user supplies a too-small bitmap
-/**
- * In the original file, using char type (without signed or unsigned) can be interpreted
- * as 'unsigned char' in some build environments, like ARM architecture.
- * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here.
- */
+
+ /**
+  * In the original file, using char type (without signed or unsigned) can be interpreted
+  * as 'unsigned char' in some build environments, like ARM architecture.
+  * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here.
+  */
 static void nsvg__fillActiveEdges(unsigned char* scanline, int len, NSVGactiveEdge* e, int maxWeight, int* xmin, int* xmax, signed char fillRule)
 {
     // non-zero winding fill