branch, master, updated. v0.7-1-g0804ea1

The branch, master has been updated via 0804ea1089c17dc9e4dd7c9d9dedb0d06be4ba98 (commit) from a7f1dfd77a48705970218a389982c95eeb11810f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=cal10n.git;a=commit;h=0804ea1089c17dc9e4dd7c9d9d... http://github.com/ceki/cal10n/commit/0804ea1089c17dc9e4dd7c9d9dedb0d06be4ba9... commit 0804ea1089c17dc9e4dd7c9d9dedb0d06be4ba98 Author: Ceki Gulcu <ceki@qos.ch> Date: Fri Sep 4 18:03:42 2009 +0200 text about colors being an example diff --git a/cal10n-site/src/site/pages/manual.html b/cal10n-site/src/site/pages/manual.html index 0fc3ef3..26f3c85 100644 --- a/cal10n-site/src/site/pages/manual.html +++ b/cal10n-site/src/site/pages/manual.html @@ -82,9 +82,12 @@ message, CAL10N uses <code>enums</code>.</p> <p>For example, let us assume that you wanted to internationalize - color names. In CAL10N you could start by writing an enum type, - named Colors. You can choose any name for the enum type. Colors is - just the name this particular author picked.</p> + color names. No one in their right minds would just want to + internationalize three color names but probably a much larger set + of items. We are using color names just as an example. In CAL10N + you could start by writing an enum type, named Colors. You can + choose any name for the enum type. Colors is just the name this + particular author picked.</p> <pre class="prettyprint source">package com.foo.somePackage; ----------------------------------------------------------------------- Summary of changes: cal10n-site/src/site/pages/manual.html | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) hooks/post-receive -- Compiler assisted localization library
participants (1)
-
git-noreply@pixie.qos.ch