From 9e1337905c5260ab1e8c58f6b626629360f604a0 Mon Sep 17 00:00:00 2001 From: Emmanuel Venisse Date: Sat, 25 Jun 2005 13:13:05 +0000 Subject: [PATCH] Update doco for i18n sites. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@201746 13f79535-47bb-0310-9956-ffa450edef68 --- maven-site/src/site/apt/site.apt | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/maven-site/src/site/apt/site.apt b/maven-site/src/site/apt/site.apt index def6e00f90..8bd61f8eb9 100644 --- a/maven-site/src/site/apt/site.apt +++ b/maven-site/src/site/apt/site.apt @@ -207,17 +207,19 @@ m2 site:site site:deploy be generated at the root of the site, with a copy of the French translation of the site in the <<>> subdirectory. To add your own content for that translation instead of using the default, place a subdirectory with that locale - name in your individual content directories. For example: + name in your site directory and create a new site descriptor with the locale in the file name. For example: ------------------- +- src/ +- site/ +- apt/ - | +- fr/ - | | +- index.apt (French version) | +- index.apt (Default version) - +- site.xml + +- fr/ + | +- apt/ + | | +- index.apt (French version) + +- site.xml (Default site descriptor) + +- site_fr.xml (French site descriptor) -------------------- - ~~TODO: what about translating site.xml? + With one site descriptor by language, translated site can evolve independently.