You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Alastair Maw <al...@mxtelecom.com> on 2007/09/07 17:33:55 UTC
Calling all translators - UrlValidator translation
Hi folks,
I've just added a UrlValidator into trunk (WICKET-832, thanks Vincent
Demay!).
We're unfortunately lacking translations for the default error message
in most languages. If you can help out for any of our supported
languages, please shout. Feel free to e-mail me them directly, or reply
to this thread with them. (You needn't bother with a proper patch unless
you want to.)
The English in question is:
'${input}' is not a valid URL.
Best regards,
Al
--
Alastair Maw
MX Telecom
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Eelco Hillenius <ee...@gmail.com>.
On 9/26/07, Cristina <cr...@acm.org> wrote:
>
> Hi Al,
>
> the Portuguese (pt_BR) translation of the error message is:
>
> '${input}' não é uma URL válida.
>
> I can complete/review the existing pt_BR translations if needed... Please
> let me know if this is the case.
That would be very welcome. Thanks,
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Cristina <cr...@acm.org>.
Hi Al,
the Portuguese (pt_BR) translation of the error message is:
'${input}' não é uma URL válida.
I can complete/review the existing pt_BR translations if needed... Please
let me know if this is the case.
Regards,
Cristina
Alastair Maw-2 wrote:
>
> [...]
> We're unfortunately lacking translations for the default error message
> in most languages. If you can help out for any of our supported
> languages, please shout. Feel free to e-mail me them directly, or reply
> to this thread with them. (You needn't bother with a proper patch unless
> you want to.)
>
> The English in question is:
> '${input}' is not a valid URL.
> [...]
>
--
View this message in context: http://www.nabble.com/Calling-all-translators---UrlValidator-translation-tf4401987.html#a12912445
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by dtoffe <dt...@yahoo.com.ar>.
There is a small typo in:
EmailAddressValidator='${input}' no es una direcion de correo electronico
valida.
Should be "direccion" instead of "direcion". There are also some
missing accents, I'll post the correct Unicode chars when I figure out how.
Daniel
--
View this message in context: http://www.nabble.com/Calling-all-translators---UrlValidator-translation-tf4401987.html#a12562898
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by dtoffe <dt...@yahoo.com.ar>.
OK found it browsing 1.3 beta. The string you want for:
The English in question is:
'${input}' is not a valid URL.
is
'${input}' no es una URL válida.
Daniel
dtoffe wrote:
>
> As of v. 1.2.6, I see there is no spanish .properties translation
> file, if it's not already done in 1.3 I can contribute it.
>
> Daniel
>
>
> Alastair Maw-2 wrote:
>>
>> Hi folks,
>>
>> I've just added a UrlValidator into trunk (WICKET-832, thanks Vincent
>> Demay!).
>>
>> We're unfortunately lacking translations for the default error message
>> in most languages. If you can help out for any of our supported
>> languages, please shout. Feel free to e-mail me them directly, or reply
>> to this thread with them. (You needn't bother with a proper patch unless
>> you want to.)
>>
>> The English in question is:
>> '${input}' is not a valid URL.
>>
>> Best regards,
>>
>> Al
>>
>
>
--
View this message in context: http://www.nabble.com/Calling-all-translators---UrlValidator-translation-tf4401987.html#a12562776
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by dtoffe <dt...@yahoo.com.ar>.
As of v. 1.2.6, I see there is no spanish .properties translation file,
if it's not already done in 1.3 I can contribute it.
Daniel
Alastair Maw-2 wrote:
>
> Hi folks,
>
> I've just added a UrlValidator into trunk (WICKET-832, thanks Vincent
> Demay!).
>
> We're unfortunately lacking translations for the default error message
> in most languages. If you can help out for any of our supported
> languages, please shout. Feel free to e-mail me them directly, or reply
> to this thread with them. (You needn't bother with a proper patch unless
> you want to.)
>
> The English in question is:
> '${input}' is not a valid URL.
>
> Best regards,
>
> Al
>
--
View this message in context: http://www.nabble.com/Calling-all-translators---UrlValidator-translation-tf4401987.html#a12561837
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Gerolf Seitz <ge...@gmail.com>.
hi al,
here are all missing german translations:
StringValidator.exact='${input}' ist nicht exakt ${exact} Zeichen lang.
CreditCardValidator=Die Kreditkartennummer ist ung\u00fcltig.
UrlValidator='${input}' ist keine g\u00fcltige URL.
i guess you could use that for the swiss translation too.
gerolf
On 9/7/07, Alastair Maw <al...@mxtelecom.com> wrote:
>
> Hi folks,
>
> I've just added a UrlValidator into trunk (WICKET-832, thanks Vincent
> Demay!).
>
> We're unfortunately lacking translations for the default error message
> in most languages. If you can help out for any of our supported
> languages, please shout. Feel free to e-mail me them directly, or reply
> to this thread with them. (You needn't bother with a proper patch unless
> you want to.)
>
> The English in question is:
> '${input}' is not a valid URL.
>
> Best regards,
>
> Al
>
> --
> Alastair Maw
> MX Telecom
> Tel: +44 (0) 845 666 7778
> http://www.mxtelecom.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Calling all translators - UrlValidator translation
Posted by Eelco Hillenius <ee...@gmail.com>.
On 9/25/07, Martijn Dashorst <ma...@gmail.com> wrote:
> I doubt this is license compatible. GPL all around!
I also don't see how we should integrate it in a smooth way the first place.
What I'd be more interested in, is not those particular libraries, but
to make maintaining our resource bundles less ad-hoc.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Martijn Dashorst <ma...@gmail.com>.
On 9/26/07, Reinout van Schouwen <re...@gmail.com> wrote:
> Maybe this thread will convince you that the Apache License and LGPLv3
> are perfectly mixable without requiring the end result to be released
> under LGPL:
>
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200706.mbox/browser
Excuse me for not reading a thread of ~40 messages and try to distill
whether or not ASL is compatible with GPL3, when the canonical source
(the link I provided) for license compatibility for Apache projects
doesn't state that GPL3 is safe for inclusion in Apache projects.
> > Furthermore, the *or newer* clause does not GPL v3
> > make.
>
> Umm... what do you mean? LGPLv3 is not a newer version of LGPLv2.1?
It means that:
1. Until Apache has an official, documented policy that embraces GPL 3
I don't even want to look at code that is currently (L)GPL 2 licensed
2. Even if Apache says GPL3 is compatible and acceptable, that doesn't
mean originally GPL2 licensed code is automatically covered, even if
there is a small sentence 'claiming' to be so.
> Then there is gettext-commons, that Al Maw linked to. It's a library
> that makes it easy to retrieve strings from gettext catalogs in Java. It
> is not GPL but LGPL as pointed out previously.
LGPL is just as off limits as the GPL!
> Are you suggesting that translations become a derivative work of a
> GPL'ed $program simply by virtue of having been touched in memory by
> said $program?
If the translations come from a library or archive distributed with
said $program then YES!
> The reason called for .po files (instead of .properties bundles) in the
> first place, is that a lot of gettext-based tools exist for translators
> to make their task more comfortable.
.po files are not standard Java. -> not many people from the Wicket
community will understand them. Properties are: infact they are
supported by all major Java IDE's.
So why change to something that is not supported by mainstream Java
tools, and has a problematic license?
The suggestion and intent is good and are appreciated, but IMO it is
not going to fly: I see too many traps along the road.
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Reinout van Schouwen <re...@gmail.com>.
Hi Martijn,
Op woensdag 26-09-2007 om 08:49 uur [tijdzone +0200], schreef Martijn Dashorst:
> I think it is still not possible to include (L)GPL based dependencies
> in Apache software: the cannonical list [1] doesn't show GPL v3 as
> being acceptible.
Maybe this thread will convince you that the Apache License and LGPLv3
are perfectly mixable without requiring the end result to be released
under LGPL:
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200706.mbox/browser
> Furthermore, the *or newer* clause does not GPL v3
> make.
Umm... what do you mean? LGPLv3 is not a newer version of LGPLv2.1?
> The default gettext translations /are/ IMO GPL, as they are supplied
> by gettext.
Plain Gettext is GPL, but it's not some process running in the
background. It's a collection of completely independent utilities that
extract strings from source code into a human editable message catalog,
and compile it to a binary format again. It isn't executed during
runtime of the localized application.
Then there is gettext-commons, that Al Maw linked to. It's a library
that makes it easy to retrieve strings from gettext catalogs in Java. It
is not GPL but LGPL as pointed out previously.
Are you suggesting that translations become a derivative work of a
GPL'ed $program simply by virtue of having been touched in memory by
said $program?
> derivative works, and are hence (L)GPL licensed. If you want us to use
> gettext to provide our own translations under the ASL, then why not
> continue with the current bundles?
The reason called for .po files (instead of .properties bundles) in the
first place, is that a lot of gettext-based tools exist for translators
to make their task more comfortable.
> It is not like we are going to
> provide complete translations for all languages.
It would certainly be nice to have a good coverage, though!
regards,
--
Reinout van Schouwen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Martijn Dashorst <ma...@gmail.com>.
I think it is still not possible to include (L)GPL based dependencies
in Apache software: the cannonical list [1] doesn't show GPL v3 as
being acceptible. Furthermore, the *or newer* clause does not GPL v3
make.
The default gettext translations /are/ IMO GPL, as they are supplied
by gettext. Generating bundles based on those translations creates
derivative works, and are hence (L)GPL licensed. If you want us to use
gettext to provide our own translations under the ASL, then why not
continue with the current bundles? It is not like we are going to
provide complete translations for all languages.
Martijn
[1] http://people.apache.org/~cliffs/3party.html
On 9/26/07, Reinout van Schouwen <re...@gmail.com> wrote:
> Hi Martijn,
>
> Op woensdag 26-09-2007 om 00:57 uur [tijdzone +0200], schreef Martijn
> Dashorst:
> > LGPL is also problematic for Apache projects.
>
> Are you sure? I don't think this holds any more:
>
> http://gettext-commons.googlecode.com/svn/trunk/README states
> "This library is free software; you can redistribute it and/or
> modify it under the terms of the GNU Lesser General Public
> License as published by the Free Software Foundation; either
> version 2.1 of the License, or (at your option) _any_later_version_."
>
> (emphasis mine)
>
> As you may know the Free Software Foundation has worked with Apache to
> make version 3 of its licenses compatible with the Apache license.
> Version 3 is available since a few months now. The article on
> http://blogs.zdnet.com/Burnette/?p=153 backs up what I'm saying:
>
> "In other words, LGPL code can be combined with code using any other
> license, whether free, open, or proprietary. Unlike LGPLv2, this version
> makes it very clear that linking or combining in any way is allowed. "
>
> > And we can't use the texts coming out of such tools since they are (L)GPL too.
>
> Are you saying that user-created external data (translations) becomes
> licensed under the same license as the (L)GPL program used to process
> it? Sorry but I find that hard to believe-- I might have missed
> something, but as far as I know, it works this way: the original author
> of the translation retains copyright but licenses his work for
> distribution under the same conditions as the accompanying program. Much
> like regular code, actually.
>
> regards,
>
> --
> Reinout van Schouwen
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Reinout van Schouwen <re...@gmail.com>.
Hi Martijn,
Op woensdag 26-09-2007 om 00:57 uur [tijdzone +0200], schreef Martijn
Dashorst:
> LGPL is also problematic for Apache projects.
Are you sure? I don't think this holds any more:
http://gettext-commons.googlecode.com/svn/trunk/README states
"This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) _any_later_version_."
(emphasis mine)
As you may know the Free Software Foundation has worked with Apache to
make version 3 of its licenses compatible with the Apache license.
Version 3 is available since a few months now. The article on
http://blogs.zdnet.com/Burnette/?p=153 backs up what I'm saying:
"In other words, LGPL code can be combined with code using any other
license, whether free, open, or proprietary. Unlike LGPLv2, this version
makes it very clear that linking or combining in any way is allowed. "
> And we can't use the texts coming out of such tools since they are (L)GPL too.
Are you saying that user-created external data (translations) becomes
licensed under the same license as the (L)GPL program used to process
it? Sorry but I find that hard to believe-- I might have missed
something, but as far as I know, it works this way: the original author
of the translation retains copyright but licenses his work for
distribution under the same conditions as the accompanying program. Much
like regular code, actually.
regards,
--
Reinout van Schouwen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Martijn Dashorst <ma...@gmail.com>.
LGPL is also problematic for Apache projects. And we can't use the
texts coming out of such tools since they are (L)GPL too.
Martijn
On 9/25/07, Reinout van Schouwen <re...@gmail.com> wrote:
> Hi Martijn,
>
> Op dinsdag 25-09-2007 om 19:50 uur [tijdzone +0200], schreef Martijn
> Dashorst:
> > I doubt this is license compatible. GPL all around!
>
> What are you referring to exactly?
> http://gettext-commons.googlecode.com/svn/trunk/LICENSE.txt is LGPL.
>
> The gettext utilities may be GPL, but they are not linked to directly or
> indirectly as far as I can see. They are only used to create and manage
> the message catalogs.
>
> In fact I am 100% certain that an LGPL library like GTK+ has been
> localized with gettext support for years without apparent license
> problems!
>
> regards,
>
> --
> Reinout van Schouwen
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Reinout van Schouwen <re...@gmail.com>.
Hi Martijn,
Op dinsdag 25-09-2007 om 19:50 uur [tijdzone +0200], schreef Martijn
Dashorst:
> I doubt this is license compatible. GPL all around!
What are you referring to exactly?
http://gettext-commons.googlecode.com/svn/trunk/LICENSE.txt is LGPL.
The gettext utilities may be GPL, but they are not linked to directly or
indirectly as far as I can see. They are only used to create and manage
the message catalogs.
In fact I am 100% certain that an LGPL library like GTK+ has been
localized with gettext support for years without apparent license
problems!
regards,
--
Reinout van Schouwen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Martijn Dashorst <ma...@gmail.com>.
I doubt this is license compatible. GPL all around!
Martijn
On 9/25/07, Al Maw <wi...@almaw.com> wrote:
> Eelco Hillenius wrote:
> > On 9/25/07, Reinout van Schouwen <re...@gmail.com> wrote:
> >> Op vrijdag 07-09-2007 om 16:33 uur [tijdzone +0100], schreef Alastair
> >> Maw:
> >>
> >>> We're unfortunately lacking translations for the default error message
> >>> in most languages. If you can help out for any of our supported
> >>> languages, please shout. Feel free to e-mail me them directly, or reply
> >>> to this thread with them. (You needn't bother with a proper patch unless
> >>> you want to.)
> >>>
> >>> The English in question is:
> >>> '${input}' is not a valid URL.
> >> As an Free software project, I'm a bit surprised Wicket doesn't use the
> >> de facto way of supporting translations in open source land: gettext (or
> >> does it?)
> >>
> >> There's a bunch of specialized tools available for the gettext .po
> >> format that free software translators have on their belt. Surely that
> >> would work more producively than asking for translations on a mailing
> >> list each time a new string is added!
> >>
> >> Using the XLIFF format together with Sun's translation editor or OmegaT
> >> would be another viable option.
> >
> > I agree, we could do this in a less ad-hoc fashion. It would be yet
> > another thing to set-up though. Do you have a suggestion how we could
> > integrate something like this so that it works well for the whole team
> > and with our build process etc?
>
> See:
> http://www.gnu.org/software/gettext/manual/html_node/Java.html
> And also:
> http://xnap-commons.sourceforge.net/gettext-commons/
> http://code.google.com/p/gettext-commons/wiki/Tutorial
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Al Maw <wi...@almaw.com>.
Eelco Hillenius wrote:
> On 9/25/07, Reinout van Schouwen <re...@gmail.com> wrote:
>> Op vrijdag 07-09-2007 om 16:33 uur [tijdzone +0100], schreef Alastair
>> Maw:
>>
>>> We're unfortunately lacking translations for the default error message
>>> in most languages. If you can help out for any of our supported
>>> languages, please shout. Feel free to e-mail me them directly, or reply
>>> to this thread with them. (You needn't bother with a proper patch unless
>>> you want to.)
>>>
>>> The English in question is:
>>> '${input}' is not a valid URL.
>> As an Free software project, I'm a bit surprised Wicket doesn't use the
>> de facto way of supporting translations in open source land: gettext (or
>> does it?)
>>
>> There's a bunch of specialized tools available for the gettext .po
>> format that free software translators have on their belt. Surely that
>> would work more producively than asking for translations on a mailing
>> list each time a new string is added!
>>
>> Using the XLIFF format together with Sun's translation editor or OmegaT
>> would be another viable option.
>
> I agree, we could do this in a less ad-hoc fashion. It would be yet
> another thing to set-up though. Do you have a suggestion how we could
> integrate something like this so that it works well for the whole team
> and with our build process etc?
See:
http://www.gnu.org/software/gettext/manual/html_node/Java.html
And also:
http://xnap-commons.sourceforge.net/gettext-commons/
http://code.google.com/p/gettext-commons/wiki/Tutorial
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Eelco Hillenius <ee...@gmail.com>.
On 9/25/07, Reinout van Schouwen <re...@gmail.com> wrote:
> Op vrijdag 07-09-2007 om 16:33 uur [tijdzone +0100], schreef Alastair
> Maw:
>
> > We're unfortunately lacking translations for the default error message
> > in most languages. If you can help out for any of our supported
> > languages, please shout. Feel free to e-mail me them directly, or reply
> > to this thread with them. (You needn't bother with a proper patch unless
> > you want to.)
> >
> > The English in question is:
> > '${input}' is not a valid URL.
>
> As an Free software project, I'm a bit surprised Wicket doesn't use the
> de facto way of supporting translations in open source land: gettext (or
> does it?)
>
> There's a bunch of specialized tools available for the gettext .po
> format that free software translators have on their belt. Surely that
> would work more producively than asking for translations on a mailing
> list each time a new string is added!
>
> Using the XLIFF format together with Sun's translation editor or OmegaT
> would be another viable option.
I agree, we could do this in a less ad-hoc fashion. It would be yet
another thing to set-up though. Do you have a suggestion how we could
integrate something like this so that it works well for the whole team
and with our build process etc?
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Reinout van Schouwen <re...@gmail.com>.
Op vrijdag 07-09-2007 om 16:33 uur [tijdzone +0100], schreef Alastair
Maw:
> We're unfortunately lacking translations for the default error message
> in most languages. If you can help out for any of our supported
> languages, please shout. Feel free to e-mail me them directly, or reply
> to this thread with them. (You needn't bother with a proper patch unless
> you want to.)
>
> The English in question is:
> '${input}' is not a valid URL.
As an Free software project, I'm a bit surprised Wicket doesn't use the
de facto way of supporting translations in open source land: gettext (or
does it?)
There's a bunch of specialized tools available for the gettext .po
format that free software translators have on their belt. Surely that
would work more producively than asking for translations on a mailing
list each time a new string is added!
Using the XLIFF format together with Sun's translation editor or OmegaT
would be another viable option.
regards,
--
Reinout van Schouwen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Calling all translators - UrlValidator translation
Posted by Kent Tong <ke...@cpttm.org.mo>.
Alastair Maw-2 wrote:
>
> The English in question is:
> '${input}' is not a valid URL.
>
The Traditional Chinese (zh_TW) version is:
UrlValidator='${input}'\u4e0d\u662f\u4e00\u500b\u5408\u6cd5\u7684URL\u3002
The Simplified Chinese (zh_CN) version is:
UrlValidator='${input}'\u4e0d\u662f\u4e00\u4e2a\u5408\u6cd5\u7684URL\u3002
--
View this message in context: http://www.nabble.com/Calling-all-translators---UrlValidator-translation-tf4401987.html#a12569613
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org