[
http://jira.codehaus.org/browse/MSITE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-248:
----------------------------------
Component/s: internationalization
> Internationalization: Do not duplicate css files and image resources.
> ----------------------------------------------------------------------
>
> Key: MSITE-248
> URL: http://jira.codehaus.org/browse/MSITE-248
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Components: internationalization
> Affects Versions: 2.0-beta-5
> Reporter: Alexander Hars
>
> Currently, Maven copies the skin's css files and image resources into each
> locale directory. This leads to redundancy and has serious drawbacks when the
> developer adds their own .css files (which most developers will do). If the
> .css files are not packaged into a skin, then the developer has to copy each
> change to the .css file into teach locale. (And we should not expect a
> developer to create skin for a single project.).
> Redundant resources also additional drawbacks. For example, if the localized
> files are distributed as help files for a Java application we unnecessarily
> increase the size of our distribution.
> It would be much better to use a single location for all css files and image
> resource (Of course, this does not prevent the developer from adding
> localized css files or image resources, should they be needed).
> The solution is simple: save the css files and resources only once below the
> root directory. Then use relative links that point from the localized pages
> to the root.
> This can easily be done if the maven template could distinguish between the
> localized directory for the default locale and the other locales (would
> require another property to be passed to Velocity). It would even be simpler
> if the directory structure treated all locales as equals, as is best practice
> for internationalized applications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
