I see. My report looks a bit different. see attached screenshot.
your's is indeed too wide.
Rather than replacing axis (put files in columns) I'd like to try
making the columns less wide, mainly by reducing text in cells and
column headers.
detailed file specific table that would list all missing or
not-translated property keys could be added as well.
Milos
On 7/22/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Here's an example of how the report looks:
>
http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.html
>
> Dennis Lundberg wrote:
> > Hi Milos,
> >
> > I've had a look at the report mojo, and it really cool. I tested
it on
> > maven-project-info-reports-plugin and it shows that some work
needs to
> > be done on the translations.
> >
> > I'm not happy with the layout of the report though. When I
configure all
> > 13 locales that are available for the maven-p-i-r-plugin it gets more
> > that a little wide. I'd like to change rows into columns and vice
versa.
> > Perhaps create one table per resource bundle. I do think that the
"main"
> > counter-report on the number of properties for each bundle should be
> > separate. What I mean is that if you don't configure any locales
you get
> > the counter-report. If you do configure locales you get the
> > locale-report. What do you think?
> >
> > Milos Kleint wrote:
> >> the pseudo localization mojo is there
> >>
(http://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/l10n-maven-plugin/
> >> Along with a simple report that lists all resource bundles in the
> >> project and for selected locales the completeness of translation.
> >>
> >> Milos
> >>
> >> On 7/20/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >>> Do you know of a plugin that checks that all bundle properties are
> >>> present for all localizations? If not, that would be a sweet
addition.
> >>>
> >>> Perhaps the plugin could be called localization-maven-plugin to
> >>> accommodate for such enhancements in the future.
> >>>
> >>> Milos Kleint wrote:
> >>> > Hello,
> >>> >
> >>> > I've hacked together a plugin that might be worth sharing. I'm
> >>> > wondering if it's ok to put in sandbox.
> >>> >
> >>> > it will process all bundle properties files in the project and
> >>> > performs a pseudolocalization.
> >>> > That means each property value gets replaced with a "${prefix}
> >>> > ${old_value} ${suffix} value and the result is placed in
> >>> > *_xx.properties where xx is the pseudolocale.
> >>> > That way one can check one's application for correct and complete
> >>> > Internationalization without actually having the
chinese/japanese/...
> >>> > translations at hand.
> >>> >
> >>> > more on pseudolocalization:
> >>> > http://developers.sun.com/solaris/articles/i18n/I18N_Testing.html
> >>> > more on java I18N:
> >>> >
http://java.sun.com/developer/technicalArticles/Intl/ResourceBundles/
> >>> >
> >>> > Cheers.
> >>> >
> >>> > Milos Kleint
> >>> >
> >>> >
---------------------------------------------------------------------
> >>> > To unsubscribe from this list please visit:
> >>> >
> >>> > http://xircles.codehaus.org/manage_email
> >>> >
> >>>
> >>>
> >>> --
> >>> Dennis Lundberg
> >>>
> >>>
---------------------------------------------------------------------
> >>> To unsubscribe from this list please visit:
> >>>
> >>> http://xircles.codehaus.org/manage_email
> >>>
> >>>
> >>
> >>
---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
