On 7/23/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Milos Kleint wrote:
> this is how the report would look like when all labels are reduced in
> size. Looks ok IMHO. We would need to write a legend though
> describing what means what.
I still think that changing axis is the way to go. The number of
localizations could be *very* large. I spoke with someone at ApacheCon
and he described a piece of software that were to be translated into
140+ languages.
I would argue that is not the common case though. Even internationally
popular stuff like azureus seems to have only around 40. which is
still wider than the browser screen though.
most projects will have just a handful I believe..
On the other hand the different counts that we have is small and I don't
see it growing either. Something like this:
org/codehaus/mevenide/netbeans/customizer/Bundle.properties (71 properties)
+---------+--------------+------------+---------------------+
| Locale | Missing keys | Extra keys | Non-translated keys |
+---------+--------------+------------+---------------------+
| zh_CN | | 1 | 26 |
+---------+--------------+------------+---------------------+
| pt_BR | Missing file |
+---------+--------------+------------+---------------------+
| ja | 5 | 3 | 66 |
+---------+--------------+------------+---------------------+
the problem here is that you cannot use the files themselves as
columns. So eventually if there is more than 1 resource bundle file,
you end up with multiple, rather narrow tables. That's something I'd
like to avoid for the summary.
as you mentioned earlier, the detailed reports with listings of wrong
keys shall be probably organized by locale.
Milos
> I've noticed a few false positives, eg. in the "hu" translation. If
> the localized string value is something like "ArtifactId" or "URL" it
> often doesn't get translated, which the report then lists as either
> "missing" or "non-translated".
>
> Comments, ideas?
>
> Milos
>
> On 7/22/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
>> 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
>> >
>> >
>>
>>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> 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
