From: Bruno Haible <bruno@clisp.org>
Date: Mon, 5 Nov 2001 10:42:00 +0000 (+0000)
Subject: Improve comments for Javadoc.
X-Git-Tag: v0.11~338
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=895b0f40c93cb7ebd8d486f789834ea860a40c88;p=thirdparty%2Fgettext.git

Improve comments for Javadoc.
---

diff --git a/intl-java/gnu/gettext/GettextResource.java b/intl-java/gnu/gettext/GettextResource.java
index 5f358c537..f0a5711d0 100644
--- a/intl-java/gnu/gettext/GettextResource.java
+++ b/intl-java/gnu/gettext/GettextResource.java
@@ -36,10 +36,12 @@ import java.util.*;
  *       In the GNU gettext approach, the keys are the English/ASCII version
  *       of the messages.
  *   <LI>In the Sun approach, the translation files are called
- *       "Resource_locale.properties" and have non-ASCII characters encoded
- *       in the Java \-unnnn syntax. Very few editors can natively display
- *       international characters in this format. In the GNU gettext
- *       approach, the translation files are called "Resource.locale.po"
+ *       "<VAR>Resource</VAR>_<VAR>locale</VAR>.properties" and have non-ASCII
+ *       characters encoded in the Java
+ *       <CODE>\</CODE><CODE>u<VAR>nnnn</VAR></CODE> syntax. Very few editors
+ *       can natively display international characters in this format. In the
+ *       GNU gettext approach, the translation files are called
+ *       "<VAR>Resource</VAR>.<VAR>locale</VAR>.po"
  *       and are in the encoding the translator has chosen. Many editors
  *       can be used. There are at least three GUI translating tools
  *       (Emacs PO mode, KDE KBabel, GNOME gtranslator).