Re: Translation help wanted

[Woonsan Ko]

On Tue, Nov 13, 2018 at 7:02 PM André Warnier (tomcat)  wrote:
>
> Ok, I take it back. I don't think there's an AI smart enough to translate 
> this one :

+1. ;-)

While translating only 3% for Korean, I already met some challenging
items and it was not easy to find right words.
In my case, it was helpful to look up the source code as well in that case.

For example,

Unable to replicate out data for a AbstractReplicatedMap.get operation
java.org.apache.catalina.tribes.tipis.zzz.abstractReplicatedMap.unable.get

The first line is the English message, and the second is a hint for
the message key. Just remove before "zzz." and find
"abstractReplicatedMap.unable.get" in the .java files from [1]. Then
the message can be better understood, or we could get a better
translation than the default one.

AI is cheap at the moment. Cheap word is cheap to readers.

Regards,

Woonsan

[1] https://github.com/apache/tomcat.git

>
> "The attribute directive (declared in line [{1}] and whose name attribute is 
> [{0}], the
> value of this name-from-attribute attribute) must be of type 
> java.lang.String, is
> "required" and not a "rtexprvalue"."
>
> On 13.11.2018 18:54, André Warnier (tomcat) wrote:
> > On 13.11.2018 18:12, Mark Thomas wrote:
> >> Removing the [OT] marker as I think this is very much on topic.
> >>
> >> On 13/11/2018 15:33, André Warnier (tomcat) wrote:
> >>> Holy Smoke (Fumée Sacrée | Sagrado Humo | Heilige Rauch) !
> >>> How many messages are in that code ?
> >>
> >> Currently there are 2747 unique terms.
> >>
> >>> Seems time to add some AI-translate add-on to the code.
> >>
> >> That is supported but it has to be paid for. That was something I was
> >> thinking about. I have 10k characters of free translation (POEditor uses
> >> either Google translate or Microsoft Automatic Translation) with my
> >> POEditor account. The Tomcat messages average ~67.5 characters per
> >> message so those free credits should be able to translate just under 150
> >> messages.
> >>
> >> To put it another way, automatic translation of the 2000 untranslated
> >> French messages would cost less than $10 USD.
> >>
> >> Hmm. The Tomcat project has a little over GBP 800 in the bank to cover
> >> the up front costs of the next Tomca,t conference.
> >>
> >> Here is a thought. I try automatic translation of as many French
> >> messages as I can with the 10k free characters. You review them (you can
> >> filter by automatic translation and then mark them as proof read). If
> >> you think the automatic translations are worthwhile, I get the PMC to
> >> vote on spending some of that money on automatic translation. For
> >> example, if we spent ~$55 we could do automatic translation for just
> >> over 10 complete languages.
> >>
> >> Are you up for that?
> >>
> >
> > I was half-kidding, but what I was really thinking of, was a Valve which 
> > would use some AI
> > to translate the messages going out, on-the-fly.
> >
> > The vast majority of the messages which I've seen so far (and attempted to 
> > translate to
> > French), are error messages, which either go to the logs (in majority I 
> > presume), or to
> > the user as some kind of error response (of which the status codes should 
> > be identifiable).
> > A good number of terms in them (50% ?) are either untranslatable, or should 
> > not be
> > translated because they point to Classnames and the like (so, "reserved 
> > words").
> > The rest looks like a limited vocabulary and "filler" words, such as "can", 
> > "cannot",
> > "disallowed", "parameter", "directory", "request", "response", "committed" 
> > ..
> > The majority of the messages also look like they would make sense only to a 
> > public of
> > programmers, which are used to deal with english-speaking-only programming 
> > languages (only
> > Java in this case), and (I believe) are not so picky about the finer points 
> > of style or
> > syntax (well, at least not the ones I know) ;-).
> > The thing is also that one really needs such a translation only when things 
> > go wrong or
> > during development/testing, so it could be turned off (default) and on only 
> > when needed,
> > using some dynamic parameter e.g. (the Manager, anyone ?).
> >
> > That all looks to me like it may make sense, and it should not be so 
> > difficult, to apply
> > some automated (and optional) translation to them on-the-fly.  And such a 
> > thing may save
> > *a lot* of maintenance and contributed time over the years, don't you think 
> > ?
> >
> > Note that this is not in any way meant to denigrate the enthousiasm and 
> > literary talent of
> > the people having contributed so far. But let's face it : due to the very 
> > nature of the
> > beast itself, to the length limit etc., most of what comes out looks like 
> > Denglish or
> > Frenglish or Spanglish anyway (and has to be so, to be really helpful). So 
> > maybe we might
> > as well bite the bullet..
> > Also, AI sounds hot again nowadays, and having the first Apache software 

RE: Apache Tomcat Deploying war file every time on AIX even though there are no changes in war file.

[David Cleary]

Mark,

Turns out it is a JDK bug.

http://www-01.ibm.com/support/docview.wss?uid=swg1IV99686
https://bugs.openjdk.java.net/browse/JDK-8177809

While it has been fixed, we currently are required to support AIX 6.1, which 
doesn't have an updated JDK because IBM no longer supports that version of AIX.

Dave

-Original Message-
From: Mark Thomas  
Sent: Monday, November 12, 2018 4:30 AM
To: users@tomcat.apache.org
Subject: Re: Apache Tomcat Deploying war file every time on AIX even though 
there are no changes in war file.

On 12/11/2018 05:36, Nagaraju Varaparla wrote:
> Mark,
>Thanks.
> I have checked the last modified time of the META-INF/war-tracker file and 
> the war file.
> I see both are same. And still tomcat re-deploying the war file.
> 
> May be the time comparison failing?

Maybe. But it is hard to see how.

Can you repeat this in a test environment? If so, I'd recreate this while 
running Tomcat with a remote debugger and put a break point in
org.apache.catalina.startup.ExpandWar.expand(Host,URL,String) to see exactly 
what is going on. Unfortunately, there isn't any additional logging available.

Mark


> 
> Thanks,
> Nagaraju.V
> 
> 
> 
> From: Mark Thomas 
> Sent: Sunday, November 11, 2018 2:06 AM
> To: Tomcat Users List 
> Subject: Re: Apache Tomcat Deploying war file every time on AIX even though 
> there are no changes in war file.
> 
> On 10/11/2018 16:35, Nagaraju Varaparla wrote:
>> Hi,
>> greetings!!
>>
>> Issue Description:
>> Apache Tomcat Deploying war file every time on AIX even though there are no 
>> changes in war file.
>> This causing all my applications are getting un-registered.
>>
>> Environment.
>> Tomcat Version: apache-tomcat-8.5.34
>> JAVA Version : IBM JAVA 
>> http://8.5.0.25
>> .25> .5.0.25> OS : IBM AIX 6.1 (AIX VERSION 6100-09-09-1717)
>>
>> Steps to reproduce:
>> 1. Set JAVA PATH to IBM JDK http://1.8.5.25.
>> 2. Download apache-tomcat-8.5.34.
>> 3. Set CATALINA_HOME as tomcat folder(apache-tomcat-8.5.34).
>> 4. we can check the version of tomcat and java with catalina.sh 
>> version 5. Create sample war file and copy to webapps folder of tomcat.
>> 6. start the tomcat (catalina.sh start) 7. Wait till tomcat explode 
>> the war file into webapps folder.(till we see the modified time of the 
>> sample folder).
>> 8. stop the tomcat (catalina.sh stop) 9. again start the tomcat 
>> (catalina.sh start)
>>
>> This will re-deploy the application. Ideally this should not happen as the 
>> war file is already deployed and not changed.
>> This is deleting the existing application and re-deploying.
>> I can see this in the log file.
>> An expanded directory [apache-tomcat-8.5.34/webapps/sample] was found 
>> with a last modified time that did not match the associated WAR. It will be 
>> deleted. > it is getting delete here Please let us know if more 
>> information is needed.
> 
> When Tomcat unpacks a WAR file it adds a file called:
> META-INF/war-tracker
> 
> in the expanded directory. The last modified time of this file is set 
> to be the same as the WAR file. When Tomcat (re-)starts, if those 
> timestamps are found to be different, Tomcat assumes the WAR was 
> updated while Tomcat was shut down and redeploys the WAR.
> 
> You need to check those timestamps and investigate what, if anything, 
> might be modifying them.
> 
> Mark
> 
> -
> To unsubscribe, e-mail: 
> users-unsubscr...@tomcat.apache.org ache.org> For additional commands, e-mail: 
> users-h...@tomcat.apache.org
> 



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Mark Thomas]

On 13/11/2018 18:08, Olaf Kock wrote:
> 
> On 13.11.18 18:12, Mark Thomas wrote:
>>
>>> Seems time to add some AI-translate add-on to the code.
>> That is supported but it has to be paid for. That was something I was
>> thinking about. I have 10k characters of free translation (POEditor uses
>> either Google translate or Microsoft Automatic Translation) with my
>> POEditor account. The Tomcat messages average ~67.5 characters per
>> message so those free credits should be able to translate just under 150
>> messages.
> 
> 
> We've been using automatic translation in Liferay for a while, but IMHO
> this didn't work out well.
> 
> Machine translations lack the context, and are rarely right (and
> accurate), but typically confusing, sometimes hillarious, partly rude
> and rather unhelpful. More than that: If even new terms will be
> automatically translated in the future, translators will always have to
> go through *everything* and identify the newly automatically translated
> strings. Not fun.
> 
> I'd recommend to not even consider it. At Liferay, which has
> considerable user-facing UI, this was a quick start, that triggered
> corrections once there was a wonky automatic translation. Plus, after a
> while we introduced a mechanism to identify newly translated strings.
> Without that, it's hard to maintain.

We do have this. POEditor will filter to show only automated
translations and we can mark them as proof-read once they have been checked.

Is any one willing to try this? If so, for which language?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Translation help wanted

[Caldarale, Charles R]

> From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
> Subject: Re: Translation help wanted

> There is no need to have an en-BR, en-US and eu-AU when simply "en" will
work.

Might need an en-EastEnders or en-Yorkshire though...

  - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.



smime.p7s
Description: S/MIME cryptographic signature

Re: Translation help wanted

[Dave Fisher]

Sent from my iPhone

> On Nov 13, 2018, at 9:36 AM, Christopher Schultz 
>  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> All,
> 
>> On 11/13/18 10:39, André Warnier (tomcat) wrote:
>>> On 13.11.2018 13:32, Rémy Maucherat wrote:
>>> On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas 
>>> wrote:
>>> 
 I'm aiming to export the translations on a regular basis to the
 Tomcat source code. How regularly will depend on the rate of
 new/updated translations but as a minimum, I'm aiming to get
 any updates into the next Tomcat 9 release.
 
>>> 
>>> Ok. Could you remove "French (MC)" ? No idea where it comes from
>>> but in Monaco they do standard French, and it's too small anyway
>>> :D
>>> 
>> 
>> You could add "French (B)" though.  There's more of us than
>> Monégasques, and we have some words all our own, for instance in
>> the numbers category. I'm sure the Swiss would agree.
>> 
>> Just kidding..
> 
> Here's the thing: lots of countries have their own dialects of various
> languages, but the root language is really the same. Nobody in Quebec
> is going to read "standard" French and misunderstand "our boat is
> sinking and we are all going to die" for "we are performing an
> existential thought-experiment"[1].
> 
> If the "standard" translation is done well, we don't need fr-* where *
> is every country where the French language is spoken. Imagine fr-US-NO
> where "NO" is "New Orleans" which speaks ... an odd assortment of
> pidgin languages that sound kind of French-y. We don't need an
> explosion of translations. There is no need to have an en-BR, en-US
> and eu-AU when simply "en" will work.
> 
> I'm sure that's the case for most other languages in the world.
> 
> There is a significant argument for zh-CN and zh-TW/zh-HK because
> mainland China almost exclusively uses Simplifies Chinese while TW/HK
> still use Traditional, and there really is a big difference, there.
> But I think that's an exception to the general rule.

The others are pt and pt-BR. 

> 
> When providing a translation for a particular language, try not to use
> colloquialisms that will only be understood by the people who live in
> your own city. This could easily happen in English if the Brits all
> used British slang for everything, which is completely indecipherable
> to Americans, etc. But it really shouldn't come up very often. There
> is always a clear way of saying something without resorting to slang.
> 
> If you are tempted to use slang, remember that not everyone will be
> able to read it. And if English is the primary language from which
> these translations will come, then using slang there will probably
> turn into something which (literally) does not translate well into
> another language. So, stick to standard, boring language, here.
> 
> - -chris
> 
> [1] https://www.youtube.com/watch?v=yR0lWICH3rY
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
> 
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvrC6kACgkQHPApP6U8
> pFhQqQ/9Gxg0YEPXcsyTGh+L0hguenaVT4pYzj+7SmQdyFSXBEl35HGHicY1zrtl
> lgXzytbZwf+bTlVrcs73pSRusN2hVGojYoctplQRssngKF8KU6biieRbC+uEqMmi
> cSCjab9YoE6N/WMLweZXxkT6gMl/bB/3msNEfTG92L6RlwglYOuXr+Hq7hSMJz4J
> FoY+MaM5QK6m4D+jAcxm2fWwAmgzUxXBvh6Sm5jB1Rb6l5Gp3cHVPvYKcN+70+wY
> PVRfq/TuO5qMCL+/w5HgSPqIGjbiqtzG5n/VegSYGA0ikFUJVDoxttodaeFEuF6t
> FvsFOb8lrs5RTT0a6eteEbI5WQA7W/dhGJrY1bIOLk6Yiujfn4EKrT5D0KLdp+9h
> Se60tuW917hMUs1WuKkz6baBpyU1BQ4QATBGMjYhuaaXQTvsj/AFBx0rD2aY6TbL
> LIWOtCxDgnxY8Bc0MLo0fEc0cvnwIWEAjqXFjB5f9oXyolTONwUaiEHUgp9Q4Ejr
> s9Z4Y+ck0S4uRDK0uhhp2Zdz+lz5hcDQ3cIFzMPFJN3jKkBhB243yXsHNgsI7ECg
> 1aNa9NQbt+imuS5B23NTDu8DJGHjYeUF6NGjCiWaIG5gWbcK2uhI0Sz4d9FLbapp
> zS/EPJMF6Vkcxaer7Qs4Y9Zod+H8IbTDnO7T9mnvrhLHgCiRYL4=
> =QX9r
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Translation help wanted

[Caldarale, Charles R]

> From: André Warnier (tomcat) [mailto:a...@ice-sa.com] 
> Subject: Re: Translation help wanted

> Ok, I take it back. I don't think there's an AI smart enough to translate
this one :

> "The attribute directive (declared in line [{1}] and whose name attribute
is [{0}], the 
> value of this name-from-attribute attribute) must be of type
java.lang.String, is 
> "required" and not a "rtexprvalue"."

Maybe we should translate it to English first...

  - Chuck

"This is the sort of bloody nonsense up with which I will not put."
(probably Churchill, in The Strand magazine)


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.



smime.p7s
Description: S/MIME cryptographic signature

Re: Translation help wanted

[Olaf Kock]

On 13.11.18 18:12, Mark Thomas wrote:



Seems time to add some AI-translate add-on to the code.

That is supported but it has to be paid for. That was something I was
thinking about. I have 10k characters of free translation (POEditor uses
either Google translate or Microsoft Automatic Translation) with my
POEditor account. The Tomcat messages average ~67.5 characters per
message so those free credits should be able to translate just under 150
messages.



We've been using automatic translation in Liferay for a while, but IMHO 
this didn't work out well.


Machine translations lack the context, and are rarely right (and 
accurate), but typically confusing, sometimes hillarious, partly rude 
and rather unhelpful. More than that: If even new terms will be 
automatically translated in the future, translators will always have to 
go through *everything* and identify the newly automatically translated 
strings. Not fun.


I'd recommend to not even consider it. At Liferay, which has 
considerable user-facing UI, this was a quick start, that triggered 
corrections once there was a wonky automatic translation. Plus, after a 
while we introduced a mechanism to identify newly translated strings. 
Without that, it's hard to maintain.


My 2 cents,

Olaf



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[tomcat]

Ok, I take it back. I don't think there's an AI smart enough to translate this 
one :

"The attribute directive (declared in line [{1}] and whose name attribute is [{0}], the 
value of this name-from-attribute attribute) must be of type java.lang.String, is 
"required" and not a "rtexprvalue"."


On 13.11.2018 18:54, André Warnier (tomcat) wrote:

On 13.11.2018 18:12, Mark Thomas wrote:

Removing the [OT] marker as I think this is very much on topic.

On 13/11/2018 15:33, André Warnier (tomcat) wrote:

Holy Smoke (Fumée Sacrée | Sagrado Humo | Heilige Rauch) !
How many messages are in that code ?


Currently there are 2747 unique terms.


Seems time to add some AI-translate add-on to the code.


That is supported but it has to be paid for. That was something I was
thinking about. I have 10k characters of free translation (POEditor uses
either Google translate or Microsoft Automatic Translation) with my
POEditor account. The Tomcat messages average ~67.5 characters per
message so those free credits should be able to translate just under 150
messages.

To put it another way, automatic translation of the 2000 untranslated
French messages would cost less than $10 USD.

Hmm. The Tomcat project has a little over GBP 800 in the bank to cover
the up front costs of the next Tomca,t conference.

Here is a thought. I try automatic translation of as many French
messages as I can with the 10k free characters. You review them (you can
filter by automatic translation and then mark them as proof read). If
you think the automatic translations are worthwhile, I get the PMC to
vote on spending some of that money on automatic translation. For
example, if we spent ~$55 we could do automatic translation for just
over 10 complete languages.

Are you up for that?



I was half-kidding, but what I was really thinking of, was a Valve which would 
use some AI
to translate the messages going out, on-the-fly.

The vast majority of the messages which I've seen so far (and attempted to 
translate to
French), are error messages, which either go to the logs (in majority I 
presume), or to
the user as some kind of error response (of which the status codes should be 
identifiable).
A good number of terms in them (50% ?) are either untranslatable, or should not 
be
translated because they point to Classnames and the like (so, "reserved words").
The rest looks like a limited vocabulary and "filler" words, such as "can", 
"cannot",
"disallowed", "parameter", "directory", "request", "response", "committed" ..
The majority of the messages also look like they would make sense only to a 
public of
programmers, which are used to deal with english-speaking-only programming 
languages (only
Java in this case), and (I believe) are not so picky about the finer points of 
style or
syntax (well, at least not the ones I know) ;-).
The thing is also that one really needs such a translation only when things go 
wrong or
during development/testing, so it could be turned off (default) and on only 
when needed,
using some dynamic parameter e.g. (the Manager, anyone ?).

That all looks to me like it may make sense, and it should not be so difficult, 
to apply
some automated (and optional) translation to them on-the-fly.  And such a thing 
may save
*a lot* of maintenance and contributed time over the years, don't you think ?

Note that this is not in any way meant to denigrate the enthousiasm and 
literary talent of
the people having contributed so far. But let's face it : due to the very 
nature of the
beast itself, to the length limit etc., most of what comes out looks like 
Denglish or
Frenglish or Spanglish anyway (and has to be so, to be really helpful). So 
maybe we might
as well bite the bullet..
Also, AI sounds hot again nowadays, and having the first Apache software which 
implements
an automatic on-the-fly translator-assistant for messages should be a hit, no ?

As a final marketing spiel, I would add that the inevitable initial vagaries of 
the
AI-assistant, would probably add much enjoyment to the arduous task of 
debugging one's
code. And if one can switch the language on the fly, it may even fulfill some 
educational
purpose.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[tomcat]

On 13.11.2018 18:12, Mark Thomas wrote:

Removing the [OT] marker as I think this is very much on topic.

On 13/11/2018 15:33, André Warnier (tomcat) wrote:

Holy Smoke (Fumée Sacrée | Sagrado Humo | Heilige Rauch) !
How many messages are in that code ?


Currently there are 2747 unique terms.


Seems time to add some AI-translate add-on to the code.


That is supported but it has to be paid for. That was something I was
thinking about. I have 10k characters of free translation (POEditor uses
either Google translate or Microsoft Automatic Translation) with my
POEditor account. The Tomcat messages average ~67.5 characters per
message so those free credits should be able to translate just under 150
messages.

To put it another way, automatic translation of the 2000 untranslated
French messages would cost less than $10 USD.

Hmm. The Tomcat project has a little over GBP 800 in the bank to cover
the up front costs of the next Tomca,t conference.

Here is a thought. I try automatic translation of as many French
messages as I can with the 10k free characters. You review them (you can
filter by automatic translation and then mark them as proof read). If
you think the automatic translations are worthwhile, I get the PMC to
vote on spending some of that money on automatic translation. For
example, if we spent ~$55 we could do automatic translation for just
over 10 complete languages.

Are you up for that?



I was half-kidding, but what I was really thinking of, was a Valve which would use some AI 
to translate the messages going out, on-the-fly.


The vast majority of the messages which I've seen so far (and attempted to translate to 
French), are error messages, which either go to the logs (in majority I presume), or to 
the user as some kind of error response (of which the status codes should be identifiable).
A good number of terms in them (50% ?) are either untranslatable, or should not be 
translated because they point to Classnames and the like (so, "reserved words").
The rest looks like a limited vocabulary and "filler" words, such as "can", "cannot", 
"disallowed", "parameter", "directory", "request", "response", "committed" ..
The majority of the messages also look like they would make sense only to a public of 
programmers, which are used to deal with english-speaking-only programming languages (only 
Java in this case), and (I believe) are not so picky about the finer points of style or 
syntax (well, at least not the ones I know) ;-).
The thing is also that one really needs such a translation only when things go wrong or 
during development/testing, so it could be turned off (default) and on only when needed, 
using some dynamic parameter e.g. (the Manager, anyone ?).


That all looks to me like it may make sense, and it should not be so difficult, to apply 
some automated (and optional) translation to them on-the-fly.  And such a thing may save 
*a lot* of maintenance and contributed time over the years, don't you think ?


Note that this is not in any way meant to denigrate the enthousiasm and literary talent of 
the people having contributed so far. But let's face it : due to the very nature of the 
beast itself, to the length limit etc., most of what comes out looks like Denglish or 
Frenglish or Spanglish anyway (and has to be so, to be really helpful). So maybe we might 
as well bite the bullet..
Also, AI sounds hot again nowadays, and having the first Apache software which implements 
an automatic on-the-fly translator-assistant for messages should be a hit, no ?


As a final marketing spiel, I would add that the inevitable initial vagaries of the 
AI-assistant, would probably add much enjoyment to the arduous task of debugging one's 
code. And if one can switch the language on the fly, it may even fulfill some educational 
purpose.




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

All,

On 11/13/18 10:39, André Warnier (tomcat) wrote:
> On 13.11.2018 13:32, Rémy Maucherat wrote:
>> On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas 
>> wrote:
>> 
>>> I'm aiming to export the translations on a regular basis to the
>>> Tomcat source code. How regularly will depend on the rate of
>>> new/updated translations but as a minimum, I'm aiming to get
>>> any updates into the next Tomcat 9 release.
>>> 
>> 
>> Ok. Could you remove "French (MC)" ? No idea where it comes from
>> but in Monaco they do standard French, and it's too small anyway
>> :D
>> 
> 
> You could add "French (B)" though.  There's more of us than
> Monégasques, and we have some words all our own, for instance in
> the numbers category. I'm sure the Swiss would agree.
> 
> Just kidding..

Here's the thing: lots of countries have their own dialects of various
languages, but the root language is really the same. Nobody in Quebec
is going to read "standard" French and misunderstand "our boat is
sinking and we are all going to die" for "we are performing an
existential thought-experiment"[1].

If the "standard" translation is done well, we don't need fr-* where *
is every country where the French language is spoken. Imagine fr-US-NO
where "NO" is "New Orleans" which speaks ... an odd assortment of
pidgin languages that sound kind of French-y. We don't need an
explosion of translations. There is no need to have an en-BR, en-US
and eu-AU when simply "en" will work.

I'm sure that's the case for most other languages in the world.

There is a significant argument for zh-CN and zh-TW/zh-HK because
mainland China almost exclusively uses Simplifies Chinese while TW/HK
still use Traditional, and there really is a big difference, there.
But I think that's an exception to the general rule.

When providing a translation for a particular language, try not to use
colloquialisms that will only be understood by the people who live in
your own city. This could easily happen in English if the Brits all
used British slang for everything, which is completely indecipherable
to Americans, etc. But it really shouldn't come up very often. There
is always a clear way of saying something without resorting to slang.

If you are tempted to use slang, remember that not everyone will be
able to read it. And if English is the primary language from which
these translations will come, then using slang there will probably
turn into something which (literally) does not translate well into
another language. So, stick to standard, boring language, here.

- -chris

[1] https://www.youtube.com/watch?v=yR0lWICH3rY
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvrC6kACgkQHPApP6U8
pFhQqQ/9Gxg0YEPXcsyTGh+L0hguenaVT4pYzj+7SmQdyFSXBEl35HGHicY1zrtl
lgXzytbZwf+bTlVrcs73pSRusN2hVGojYoctplQRssngKF8KU6biieRbC+uEqMmi
cSCjab9YoE6N/WMLweZXxkT6gMl/bB/3msNEfTG92L6RlwglYOuXr+Hq7hSMJz4J
FoY+MaM5QK6m4D+jAcxm2fWwAmgzUxXBvh6Sm5jB1Rb6l5Gp3cHVPvYKcN+70+wY
PVRfq/TuO5qMCL+/w5HgSPqIGjbiqtzG5n/VegSYGA0ikFUJVDoxttodaeFEuF6t
FvsFOb8lrs5RTT0a6eteEbI5WQA7W/dhGJrY1bIOLk6Yiujfn4EKrT5D0KLdp+9h
Se60tuW917hMUs1WuKkz6baBpyU1BQ4QATBGMjYhuaaXQTvsj/AFBx0rD2aY6TbL
LIWOtCxDgnxY8Bc0MLo0fEc0cvnwIWEAjqXFjB5f9oXyolTONwUaiEHUgp9Q4Ejr
s9Z4Y+ck0S4uRDK0uhhp2Zdz+lz5hcDQ3cIFzMPFJN3jKkBhB243yXsHNgsI7ECg
1aNa9NQbt+imuS5B23NTDu8DJGHjYeUF6NGjCiWaIG5gWbcK2uhI0Sz4d9FLbapp
zS/EPJMF6Vkcxaer7Qs4Y9Zod+H8IbTDnO7T9mnvrhLHgCiRYL4=
=QX9r
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Mark Thomas]

Removing the [OT] marker as I think this is very much on topic.

On 13/11/2018 15:33, André Warnier (tomcat) wrote:
> Holy Smoke (Fumée Sacrée | Sagrado Humo | Heilige Rauch) !
> How many messages are in that code ?

Currently there are 2747 unique terms.

> Seems time to add some AI-translate add-on to the code.

That is supported but it has to be paid for. That was something I was
thinking about. I have 10k characters of free translation (POEditor uses
either Google translate or Microsoft Automatic Translation) with my
POEditor account. The Tomcat messages average ~67.5 characters per
message so those free credits should be able to translate just under 150
messages.

To put it another way, automatic translation of the 2000 untranslated
French messages would cost less than $10 USD.

Hmm. The Tomcat project has a little over GBP 800 in the bank to cover
the up front costs of the next Tomcat conference.

Here is a thought. I try automatic translation of as many French
messages as I can with the 10k free characters. You review them (you can
filter by automatic translation and then mark them as proof read). If
you think the automatic translations are worthwhile, I get the PMC to
vote on spending some of that money on automatic translation. For
example, if we spent ~$55 we could do automatic translation for just
over 10 complete languages.

Are you up for that?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Rémy Maucherat]

On Tue, Nov 13, 2018 at 4:39 PM André Warnier (tomcat) 
wrote:

> On 13.11.2018 13:32, Rémy Maucherat wrote:
> > On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas  wrote:
> >
> >> I'm aiming to export the translations on a regular basis to the Tomcat
> >> source code. How regularly will depend on the rate of new/updated
> >> translations but as a minimum, I'm aiming to get any updates into the
> >> next Tomcat 9 release.
> >>
> >
> > Ok. Could you remove "French (MC)" ? No idea where it comes from but in
> > Monaco they do standard French, and it's too small anyway :D
> >
>
> You could add "French (B)" though.  There's more of us than Monégasques,
> and we have some
> words all our own, for instance in the numbers category. I'm sure the
> Swiss would agree.
>
> Just kidding..
>

Users can add languages, so no problem :)

Rémy

Re: Translation help wanted

[Ludovic Pénet]

Le mardi 13 novembre 2018 à 16:39 +0100, André Warnier (tomcat) a
écrit :
> On 13.11.2018 13:32, Rémy Maucherat wrote:
> > On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas 
> > wrote:
> > 
> > > I'm aiming to export the translations on a regular basis to the
> > > Tomcat
> > > source code. How regularly will depend on the rate of new/updated
> > > translations but as a minimum, I'm aiming to get any updates into
> > > the
> > > next Tomcat 9 release.
> > > 
> > 
> > Ok. Could you remove "French (MC)" ? No idea where it comes from
> > but in
> > Monaco they do standard French, and it's too small anyway :D
> > 
> 
> You could add "French (B)" though.  There's more of us than
> Monégasques, and we have some 
> words all our own, for instance in the numbers category. I'm sure the
> Swiss would agree.
> 
> Just kidding..
I was seriously wondering if it was worth adding French (Quebec), as
our cousins from the other side of the Atlantic like to translate
*everything* in French.

Well, let them request... :-)

Ludovic


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[tomcat]

On 13.11.2018 13:32, Rémy Maucherat wrote:

On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas  wrote:


I'm aiming to export the translations on a regular basis to the Tomcat
source code. How regularly will depend on the rate of new/updated
translations but as a minimum, I'm aiming to get any updates into the
next Tomcat 9 release.



Ok. Could you remove "French (MC)" ? No idea where it comes from but in
Monaco they do standard French, and it's too small anyway :D



You could add "French (B)" though.  There's more of us than Monégasques, and we have some 
words all our own, for instance in the numbers category. I'm sure the Swiss would agree.


Just kidding..



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[OT] Re: Translation help wanted

[tomcat]

Holy Smoke (Fumée Sacrée | Sagrado Humo | Heilige Rauch) !
How many messages are in that code ?
Seems time to add some AI-translate add-on to the code.

On 13.11.2018 14:50, Mark Thomas wrote:

On 13/11/2018 12:32, Rémy Maucherat wrote:

On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas  wrote:


I'm aiming to export the translations on a regular basis to the Tomcat
source code. How regularly will depend on the rate of new/updated
translations but as a minimum, I'm aiming to get any updates into the
next Tomcat 9 release.



Ok. Could you remove "French (MC)" ? No idea where it comes from but in
Monaco they do standard French, and it's too small anyway :D


Done. I wasn't sure about that one. Currently, any contributor can add a
new language. I left it open to let the community set the direction.

More generally...

I don't have any fixed rules in mind for when I'll a new language to the
Tomcat source code but the bar was set pretty low for what we had before
POEditor was being used. My gut feeling is 1-2% is sufficient.

I've just completed the first set of updates. It might be worth checking
the commits on the dev list (e.g. [1]) to make sure I haven't messed
anything up.

The community generated over 300 new translations yesterday which is
fantastic - and new translators continue to join. If you haven't
already, please spread the word.

I'm planning on making any Tomcat committers that sign up, admins for
the project.

Mark


[1] https://tomcat.markmail.org/thread/d5gt43lhgiw2miyc

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Mark Thomas]

On 13/11/2018 14:35, Arjuna Bandara wrote:
> Hi Mark,
> 
> I've visited your website,but could not found my native language 'Sinhala'.
> If your system capable of adding new languages please let me know.

It isn't my system. It isn't even the ASF's system. It is an externally
provided service. Neither I nor anyone else at the ASF has control over
which languages are supported by POEditor - although the list does seem
fairly comprehensive.

I think what you are looking for is "Sinhalese" which is available.

Mark


> 
> Regards
> Arjuna
> 
> On Mon, 12 Nov 2018 5:19 pm Mark Thomas,  wrote:
> 
>> All,
>>
>> Apache Tomcat includes some translations for error messages and parts of
>> the user interface - primarily the Manager web application. We would
>> like to improve the coverage and quality of these translations.
>> Accordingly, the Tomcat project has been set up on POEditor, a web-based
>> service for managing the translation of resource files.
>>
>> The aim is that anyone who wants to contribute to the translations (it
>> could be anything from fixing a typo in an existing translation to
>> adding support for a new language) can create an account and contribute.
>>
>> If you would like to contribute in this way then the
>> The Tomcat project can be found here:
>>
>> https://poeditor.com/join/project/NUTIjDWzrl
>>
>> Anyone should be able to join up as a contributor. If you are
>> interested, please sign up and start contributing.
>>
>> Note: All contributions will be taken as being made under the terms of
>> the Apache License version 2.
>>
>> I'm aiming to export the translations on a regular basis to the Tomcat
>> source code. How regularly will depend on the rate of new/updated
>> translations but as a minimum, I'm aiming to get any updates into the
>> next Tomcat 9 release.
>>
>> If you have any difficulties or questions, please ask here.
>>
>> Thanks,
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translation help wanted

[Arjuna Bandara]

Hi Mark,

I've visited your website,but could not found my native language 'Sinhala'.
If your system capable of adding new languages please let me know.

Regards
Arjuna

On Mon, 12 Nov 2018 5:19 pm Mark Thomas,  wrote:

> All,
>
> Apache Tomcat includes some translations for error messages and parts of
> the user interface - primarily the Manager web application. We would
> like to improve the coverage and quality of these translations.
> Accordingly, the Tomcat project has been set up on POEditor, a web-based
> service for managing the translation of resource files.
>
> The aim is that anyone who wants to contribute to the translations (it
> could be anything from fixing a typo in an existing translation to
> adding support for a new language) can create an account and contribute.
>
> If you would like to contribute in this way then the
> The Tomcat project can be found here:
>
> https://poeditor.com/join/project/NUTIjDWzrl
>
> Anyone should be able to join up as a contributor. If you are
> interested, please sign up and start contributing.
>
> Note: All contributions will be taken as being made under the terms of
> the Apache License version 2.
>
> I'm aiming to export the translations on a regular basis to the Tomcat
> source code. How regularly will depend on the rate of new/updated
> translations but as a minimum, I'm aiming to get any updates into the
> next Tomcat 9 release.
>
> If you have any difficulties or questions, please ask here.
>
> Thanks,
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: SSL Errors and Warnings with various version of Tomcat

[Richard Tearle]

On Tue, 13 Nov 2018 at 14:10, Mark Thomas  wrote:
>
> On 13/11/2018 14:00, Rémy Maucherat wrote:
> > On Tue, Nov 13, 2018 at 2:50 PM Richard Tearle <
> > richard.tea...@northgateps.com> wrote:
> >
> >> Hi
> >>
> >> Our applications are all working fine with Tomcat 8.5.34 and Tomcat
> >> Native 1.2.17; Centos 7.5; OpenSSL 1.0.2k-fips  26 Jan 2017; Oracle
> >> Java JRE 8u172
> >>
> >> On upgrading to Tomcat 8.5.35 and Tomcat Native 1.2.18, we get the
> >> following warning:
> >>
> >> 12-Nov-2018 14:37:03.459 WARNING [main]
> >> org.apache.tomcat.util.net.openssl.OpenSSLEngine. Failed
> >> getting cipher list
> >>  java.lang.Exception: Invalid Server SSL Protocol
> >> (error::lib(0):func(0):reason(0))
> >> at org.apache.tomcat.jni.SSLContext.make(Native Method)
> >> at org.apache.tomcat.util.net
> >> .openssl.OpenSSLEngine.(OpenSSLEngine.java:73)
> >>
> >
> > There was a patch porting problem in 8.5 in the jni.SSL class.
>
> Sorry. My mistake.
>
> I'll get the necessary fix back-ported for the next 8.5.x release.
>
> Mark

OK - so I just hold off until the next release - we can live with that.

Thanks all!

Richard

> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

-- 
This email is sent on behalf of Northgate Public Services (UK) Limited and 
its associated companies including Rave Technologies (India) Pvt Limited 
(together "Northgate Public Services") and is strictly confidential and 
intended solely for the addressee(s). 
If you are not the intended 
recipient of this email you must: (i) not disclose, copy or distribute its 
contents to any other person nor use its contents in any way or you may be 
acting unlawfully;  (ii) contact Northgate Public Services immediately on 
+44(0)1442 768445 quoting the name of the sender and the addressee then 
delete it from your system.
Northgate Public Services has taken reasonable 
precautions to ensure that no viruses are contained in this email, but does 
not accept any responsibility once this email has been transmitted.  You 
should scan attachments (if any) for viruses.


Northgate Public Services 
(UK) Limited, registered in England and Wales under number 00968498 with a 
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands 
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW.  Rave Technologies (India) 
Pvt Limited, registered in India under number 117068 with a registered 
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate, 
Mumbai, Maharashtra, India, 41.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: SSL Errors and Warnings with various version of Tomcat

[Mark Thomas]

On 13/11/2018 14:00, Rémy Maucherat wrote:
> On Tue, Nov 13, 2018 at 2:50 PM Richard Tearle <
> richard.tea...@northgateps.com> wrote:
> 
>> Hi
>>
>> Our applications are all working fine with Tomcat 8.5.34 and Tomcat
>> Native 1.2.17; Centos 7.5; OpenSSL 1.0.2k-fips  26 Jan 2017; Oracle
>> Java JRE 8u172
>>
>> On upgrading to Tomcat 8.5.35 and Tomcat Native 1.2.18, we get the
>> following warning:
>>
>> 12-Nov-2018 14:37:03.459 WARNING [main]
>> org.apache.tomcat.util.net.openssl.OpenSSLEngine. Failed
>> getting cipher list
>>  java.lang.Exception: Invalid Server SSL Protocol
>> (error::lib(0):func(0):reason(0))
>> at org.apache.tomcat.jni.SSLContext.make(Native Method)
>> at org.apache.tomcat.util.net
>> .openssl.OpenSSLEngine.(OpenSSLEngine.java:73)
>>
> 
> There was a patch porting problem in 8.5 in the jni.SSL class.

Sorry. My mistake.

I'll get the necessary fix back-ported for the next 8.5.x release.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: SSL Errors and Warnings with various version of Tomcat

[Rémy Maucherat]

On Tue, Nov 13, 2018 at 2:50 PM Richard Tearle <
richard.tea...@northgateps.com> wrote:

> Hi
>
> Our applications are all working fine with Tomcat 8.5.34 and Tomcat
> Native 1.2.17; Centos 7.5; OpenSSL 1.0.2k-fips  26 Jan 2017; Oracle
> Java JRE 8u172
>
> On upgrading to Tomcat 8.5.35 and Tomcat Native 1.2.18, we get the
> following warning:
>
> 12-Nov-2018 14:37:03.459 WARNING [main]
> org.apache.tomcat.util.net.openssl.OpenSSLEngine. Failed
> getting cipher list
>  java.lang.Exception: Invalid Server SSL Protocol
> (error::lib(0):func(0):reason(0))
> at org.apache.tomcat.jni.SSLContext.make(Native Method)
> at org.apache.tomcat.util.net
> .openssl.OpenSSLEngine.(OpenSSLEngine.java:73)
>

There was a patch porting problem in 8.5 in the jni.SSL class.

Rémy

Re: Translation help wanted

[Mark Thomas]

On 13/11/2018 12:32, Rémy Maucherat wrote:
> On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas  wrote:
> 
>> I'm aiming to export the translations on a regular basis to the Tomcat
>> source code. How regularly will depend on the rate of new/updated
>> translations but as a minimum, I'm aiming to get any updates into the
>> next Tomcat 9 release.
>>
> 
> Ok. Could you remove "French (MC)" ? No idea where it comes from but in
> Monaco they do standard French, and it's too small anyway :D

Done. I wasn't sure about that one. Currently, any contributor can add a
new language. I left it open to let the community set the direction.

More generally...

I don't have any fixed rules in mind for when I'll a new language to the
Tomcat source code but the bar was set pretty low for what we had before
POEditor was being used. My gut feeling is 1-2% is sufficient.

I've just completed the first set of updates. It might be worth checking
the commits on the dev list (e.g. [1]) to make sure I haven't messed
anything up.

The community generated over 300 new translations yesterday which is
fantastic - and new translators continue to join. If you haven't
already, please spread the word.

I'm planning on making any Tomcat committers that sign up, admins for
the project.

Mark


[1] https://tomcat.markmail.org/thread/d5gt43lhgiw2miyc

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

SSL Errors and Warnings with various version of Tomcat

[Richard Tearle]

Hi

Our applications are all working fine with Tomcat 8.5.34 and Tomcat
Native 1.2.17; Centos 7.5; OpenSSL 1.0.2k-fips  26 Jan 2017; Oracle
Java JRE 8u172

On upgrading to Tomcat 8.5.35 and Tomcat Native 1.2.18, we get the
following warning:

12-Nov-2018 14:37:03.459 WARNING [main]
org.apache.tomcat.util.net.openssl.OpenSSLEngine. Failed
getting cipher list
 java.lang.Exception: Invalid Server SSL Protocol
(error::lib(0):func(0):reason(0))
at org.apache.tomcat.jni.SSLContext.make(Native Method)
at 
org.apache.tomcat.util.net.openssl.OpenSSLEngine.(OpenSSLEngine.java:73)
at 
org.apache.tomcat.util.net.openssl.OpenSSLUtil.getImplementedProtocols(OpenSSLUtil.java:63)
at org.apache.tomcat.util.net.SSLUtilBase.(SSLUtilBase.java:67)
at org.apache.tomcat.util.net.SSLUtilBase.(SSLUtilBase.java:51)
at 
org.apache.tomcat.util.net.openssl.OpenSSLUtil.(OpenSSLUtil.java:42)
at 
org.apache.tomcat.util.net.openssl.OpenSSLImplementation.getSSLUtil(OpenSSLImplementation.java:36)
at 
org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:103)
at 
org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:86)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:244)
at 
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1087)
at 
org.apache.tomcat.util.net.AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:265)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:581)
at 
org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:68)
at 
org.apache.catalina.connector.Connector.initInternal(Connector.java:993)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at 
org.apache.catalina.core.StandardService.initInternal(StandardService.java:552)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at 
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:661)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)

On downgrading Tomcat Native to 1.2.17, and still keeping Tomcat
8.5.35, we get the following FATAL:

12-Nov-2018 17:24:17.474 SEVERE [https-openssl-nio-8443-exec-2]
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
 java.lang.UnsatisfiedLinkError:
org.apache.tomcat.jni.SSL.renegotiatePending(J)I
at org.apache.tomcat.jni.SSL.renegotiatePending(Native Method)
at 
org.apache.tomcat.util.net.openssl.OpenSSLEngine.getHandshakeStatus(OpenSSLEngine.java:1021)
at 
org.apache.tomcat.util.net.openssl.OpenSSLEngine.wrap(OpenSSLEngine.java:457)
at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)
at 
org.apache.tomcat.util.net.SecureNioChannel.handshakeWrap(SecureNioChannel.java:440)
at 
org.apache.tomcat.util.net.SecureNioChannel.handshake(SecureNioChannel.java:211)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1475)
at 
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

Our application is fine with Tomcat 8.5.34 and Tomcat Native 1.2.18 as well.

Our connector configuration is, which we've not changed whilst testing
various version combinations:

   






We'd like to upgrade to Tomcat 8.5.35 and Tomcat Native 1.2.18,
without the warning (our implementers get twitchy when they see
warnings, even more so when it's around SSL/TLS...)

Richard

-- 
This email is sent on behalf of Northgate Public Services (UK) Limited and 
its associated companies including Rave Technologies (India) Pvt Limited 
(together "Northgate Public Services") and is strictly confidential and 
intended solely for the addressee(s). 
If you are not the intended 
recipient of this email you must: (i) not disclose, copy or distribute its 
contents to any other person nor use its contents in 

Re: Translation help wanted

[Rémy Maucherat]

On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas  wrote:

> I'm aiming to export the translations on a regular basis to the Tomcat
> source code. How regularly will depend on the rate of new/updated
> translations but as a minimum, I'm aiming to get any updates into the
> next Tomcat 9 release.
>

Ok. Could you remove "French (MC)" ? No idea where it comes from but in
Monaco they do standard French, and it's too small anyway :D

Rémy

RE: Apache Tomcat Deploying war file every time on AIX even though there are no changes in war file.

[Nagaraju Varaparla]

Mark,
   I did not find any luck with this.
Can I try anything more ?

Thanks,
Nagaraju.V


From: Mark Thomas 
Sent: Monday, November 12, 2018 3:00 PM
To: users@tomcat.apache.org
Subject: Re: Apache Tomcat Deploying war file every time on AIX even though 
there are no changes in war file.

On 12/11/2018 05:36, Nagaraju Varaparla wrote:
> Mark,
> Thanks.
> I have checked the last modified time of the META-INF/war-tracker file and 
> the war file.
> I see both are same. And still tomcat re-deploying the war file.
>
> May be the time comparison failing?

Maybe. But it is hard to see how.

Can you repeat this in a test environment? If so, I'd recreate this
while running Tomcat with a remote debugger and put a break point in
org.apache.catalina.startup.ExpandWar.expand(Host,URL,String) to see
exactly what is going on. Unfortunately, there isn't any additional
logging available.

Mark


>
> Thanks,
> Nagaraju.V
>
>
>
> From: Mark Thomas mailto:ma...@apache.org>>
> Sent: Sunday, November 11, 2018 2:06 AM
> To: Tomcat Users List 
> mailto:users@tomcat.apache.org>>
> Subject: Re: Apache Tomcat Deploying war file every time on AIX even though 
> there are no changes in war file.
>
> On 10/11/2018 16:35, Nagaraju Varaparla wrote:
>> Hi,
>> greetings!!
>>
>> Issue Description:
>> Apache Tomcat Deploying war file every time on AIX even though there are no 
>> changes in war file.
>> This causing all my applications are getting un-registered.
>>
>> Environment.
>> Tomcat Version: apache-tomcat-8.5.34
>> JAVA Version : IBM JAVA 
>> 8.5.0.25>
>> OS : IBM AIX 6.1 (AIX VERSION 6100-09-09-1717)
>>
>> Steps to reproduce:
>> 1. Set JAVA PATH to IBM JDK 
>> 1.8.5.25>.
>> 2. Download apache-tomcat-8.5.34.
>> 3. Set CATALINA_HOME as tomcat folder(apache-tomcat-8.5.34).
>> 4. we can check the version of tomcat and java with catalina.sh version
>> 5. Create sample war file and copy to webapps folder of tomcat.
>> 6. start the tomcat (catalina.sh start)
>> 7. Wait till tomcat explode the war file into webapps folder.(till we see 
>> the modified time of the sample folder).
>> 8. stop the tomcat (catalina.sh stop)
>> 9. again start the tomcat (catalina.sh start)
>>
>> This will re-deploy the application. Ideally this should not happen as the 
>> war file is already deployed and not changed.
>> This is deleting the existing application and re-deploying.
>> I can see this in the log file.
>> An expanded directory [apache-tomcat-8.5.34/webapps/sample] was found with a 
>> last modified time that did not match the associated WAR. It will be 
>> deleted. > it is getting delete here
>> Please let us know if more information is needed.
>
> When Tomcat unpacks a WAR file it adds a file called:
> META-INF/war-tracker
>
> in the expanded directory. The last modified time of this file is set to
> be the same as the WAR file. When Tomcat (re-)starts, if those
> timestamps are found to be different, Tomcat assumes the WAR was updated
> while Tomcat was shut down and redeploys the WAR.
>
> You need to check those timestamps and investigate what, if anything,
> might be modifying them.
>
> Mark
>
> -
> To unsubscribe, e-mail: 
> users-unsubscr...@tomcat.apache.org>
> For additional commands, e-mail: 
> users-h...@tomcat.apache.org>
>


-
To unsubscribe, e-mail: 
users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: 
users-h...@tomcat.apache.org