Fix unvalid URL

* http://www.unicode.org/unicode/reports/tr15 -> http://www.unicode.org/reports/tr15

Change-Id: Idd00ecb0d548bc65c84f9f9d7f99395447cb8626
Signed-off-by: Hyunjee Kim <hj0426.kim@samsung.com>

diff --git a/src/include/utils_i18n_types.h b/src/include/utils_i18n_types.h
index f1aa8cd..551242d 100644 (file)
--- a/src/include/utils_i18n_types.h
+++ b/src/include/utils_i18n_types.h
@@ -1573,14 +1573,14 @@ typedef const void *i18n_unormalizer_h;
 
 /**
  * @brief Enumeration of constants for normalization modes.
- *               For details about standard Unicode normalization forms and about the algorithms which are also used with custom mapping tables see http://www.unicode.org/unicode/reports/tr15/
+ *               For details about standard Unicode normalization forms and about the algorithms which are also used with custom mapping tables see http://www.unicode.org/reports/tr15/
  * @since_tizen @if MOBILE 2.3 @elseif WEARABLE 2.3.1 @endif
  */
 typedef enum {
        I18N_UNORMALIZATION_COMPOSE,                      /**< Decomposition followed by composition. Same as standard NFC when using an "nfc" instance. Same as standard NFKC when using an "nfkc" instance.
-                                                                                                  For details about standard Unicode normalization forms see http://www.unicode.org/unicode/reports/tr15/ */
+                                                                                                  For details about standard Unicode normalization forms see http://www.unicode.org/reports/tr15/ */
        I18N_UNORMALIZATION_DECOMPOSE,                    /**< Map and reorder canonically. Same as standard NFD when using an "nfc" instance. Same as standard NFKD when using an "nfkc" instance.
-                                                                                                  For details about standard Unicode normalization forms see http://www.unicode.org/unicode/reports/tr15/ */
+                                                                                                  For details about standard Unicode normalization forms see http://www.unicode.org/reports/tr15/ */
        I18N_UNORMALIZATION_FCD,                                  /**< "Fast C or D" form. If a string is in this form, then further decomposition without reordering would yield the same form as DECOMPOSE.
                                                                                                   Text in "Fast C or D" form can be processed efficiently with data tables that are "canonically closed",
                                                                                                   that is, that provide equivalent data for equivalent text, without having to be fully normalized.