cvs commit: jakarta-site2/xdocs/site elsewhere.xml
tetsuya 2003/07/09 05:19:11 Modified:docs index.html docs/site elsewhere.html xdocsindex.xml xdocs/site elsewhere.xml Log: Apache Httpd WebServer 2.0.47 Released : Elsewhere News Revision ChangesPath 1.265 +1 -5 jakarta-site2/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-site2/docs/index.html,v retrieving revision 1.264 retrieving revision 1.265 diff -u -r1.264 -r1.265 --- index.html8 Jul 2003 10:43:28 - 1.264 +++ index.html9 Jul 2003 12:19:10 - 1.265 @@ -230,16 +230,12 @@ h4Other news from a href=site/news.htmlJakarta/a and a href=site/elsewhere.htmlElsewhere/a/h4 ul +lia href=site/elsewhere.html#20030709.109 July 2003 - bApache HTTPD WebServer 2.0.47/b Released/a/li lia href=site/news.html#20030708.108 July 2003 - bJakarta Newsletter Issue 9/b Released/a/li lia href=site/news.html#20030702.202 July 2003 - bJakarta Commons/b featured in OnJava article, open source conference and (forthcoming) book/a/li lia href=site/elsewhere.html#20030625.125 June 2003 - bAnt/b and bXercesJ/b win 2003 JavaWorld Awards/a /li lia href=site/elsewhere.html#20030628.124 June 2003 - bSOAP Version 1.2/b Recommendation Issued by W3C/a/li -lia href=site/elsewhere.html#20030612.112 June 2003 - bJames/b -featured on bIBM developerWorks/b/a /li -lia href=site/news.html#20030603.203 June 2003 - bJakarta Lucene/b and bCommons Digester/b -featured on bIBM developerWorks/b/a /li - lia href=site/elsewhere.html#20030528.128 May 2003 - bApache HTTPD 2.0.46/b Released/a/li /ul /blockquote /p 1.53 +24 -1 jakarta-site2/docs/site/elsewhere.html Index: elsewhere.html === RCS file: /home/cvs/jakarta-site2/docs/site/elsewhere.html,v retrieving revision 1.52 retrieving revision 1.53 diff -u -r1.52 -r1.53 --- elsewhere.html28 Jun 2003 08:30:25 - 1.52 +++ elsewhere.html9 Jul 2003 12:19:10 - 1.53 @@ -178,7 +178,30 @@ /td/tr trtd blockquote -a name=20030628.1 +a name=20030709.1 +h309 Jul 2003 - Apache Httpd WebServer 2.0.47 released/h3/a +p + The Apache Software Foundation and the Apache HTTP Server Project are + pleased to announce the tenth public release of the Apache 2.0 + HTTP Server. This Announcement notes the significant changes in + 2.0.47 as compared to 2.0.46. +/p +p + Apache Httpd WebServer 2.0.47 is available for download from + a href=http://httpd.apache.org/download.cgi;http://httpd.apache.org/download.cgi/a. +/p +p + This version of Apache is principally a security and bug fix release. + A summary of the bug fixes is given at the end of this document. + Of particular note is that 2.0.47 addresses four security + vulnerabilities. +/p +p +See a href=http://httpd.apache.org/;The Apache HTTP Server Home Page/a +for more details. +/p +hr size=1 noshade=noshade / +a name=20030628.1 h324 June 2003 - World Wide Web Consortium Issues SOAP Version 1.2 as a W3C Recommendation /h3 /a 1.212 +1 -5 jakarta-site2/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-site2/xdocs/index.xml,v retrieving revision 1.211 retrieving revision 1.212 diff -u -r1.211 -r1.212 --- index.xml 8 Jul 2003 10:43:29 - 1.211 +++ index.xml 9 Jul 2003 12:19:10 - 1.212 @@ -55,16 +55,12 @@ h4Other news from a href=site/news.htmlJakarta/a and a href=site/elsewhere.htmlElsewhere/a/h4 ul +lia href=site/elsewhere.html#20030709.109 July 2003 - bApache HTTPD WebServer 2.0.47/b Released/a/li lia href=site/news.html#20030708.108 July 2003 - bJakarta Newsletter Issue 9/b Released/a/li lia href=site/news.html#20030702.202 July 2003 - bJakarta Commons/b featured in OnJava article, open source conference and (forthcoming) book/a/li lia
Re: [i18n] Internationalization subproject sponsor?
Rob, Some differences I see The commons-resources component does not include/encourage multilingual support as a goal. It simply abstracts the source for resources. I view the i18n code as being at a higher level than what's currently in commons-resources. The Factory's in i18n could be modified to make use of the different sources found in commons-resources. It may be necessary/useful to change some of the concrete object classes to interfaces, but those changes can come if/after it becomes a subproject. I had tried to see if I could make use of commons-resources within the code early this year, but it didn't solve the problem that I was trying to solve. Robert Simpson Rob Leland wrote: Robert Simpson wrote: Andrew, In one sentence, it intends to provide a framework for internationalization of Java projects, within the Apache/Jakarta projects themselves and for users of the Apache/Jakarta code outside Apache. I am sorry for jumping in late to this thread. How does this proposal differ from the commons-resources project in the commons-sandbox that provides for internationalization? It can load resources from a properties/XML or database ? I had started out trying to see where I could make use of the Jakarta code, and eliminate duplication of effort on my part. But the one thing I ran into was most of the Jakarta subprojects do not provide for internationalization, which is a shame, because the Java SDK does quite a good job of providing support for that. That might actually be a good thing, since there currently is the opportunity to provide a framework for doing it in one place, rather than having each subproject do it differently. Robert Simpson Andrew C. Oliver wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [i18n] Internationalization subproject sponsor?
Santiago Gala, I haven't seen the Turbine localization service code, but maybe that could be separated out and used as the initial code for the Internationalization project (pretty much what I have done to date with it). Turbine might also provide some of the language translations A couple things I like about the code I've provided, is that it's pretty much a one-liner to include resources in a class or package, and that it's a static reference. Is the Turbine approach similar? As far a document and resource translation, I'm not sure if you are referring to machine translation, or human translation. My focus has been on human translation, mainly because machine translation is still pretty far from perfect. There could be APIs for interfaces to various machine translation tools, such as Systransoft, but I think that should be a later, secondary priority. Even if there was support for machine translation, I would prefer that it could be augmented by human proofreading and revision. So it's probably just as easy to let the language translator use whatever machine translation tool s/he prefers. As opposed to something that needs to be coordinated with each Apache project, the Internationalization subproject should simply provide a common means for Apache projects to provide for internationalization. However, because the language translations for an Apache subproject should probably be distributed with those other subprojects, the InternationalizationLibrary for those subprojects would be included with those subprojects themselves, not the i18n subproject. I think the relationship between the other subprojects and i18n should be loose and unidirectional. OTOH, the InternationalizationLibrary's included with i18n would be more general application- or industry-specific (security, accounting, medical, etc). Things that would get re-used fairly often. Robert Simpson Santiago Gala wrote: Robert Simpson escribió: I also fear that if I go back to simply continuing the development of the code myself, that eventually the need in Jakarta will be recognized, but I will be too far along at that point to convert everything to it. Or worse yet, the need will be recognized at different times within each Jakarta subproject, resulting in each subproject doing internationalization their own way. Jetspeed is already using i18n (or is it l10n?) for most of its strings. We use the Turbine 2.2 localization service for client specific ResourceBundles lookup and caching. I think Tomcat has also some effort already done. The main problem I see in your proposal is not coding it, but getting any/some/most of the jakarta projects to use the code, and agree in ways to handle the files back and forth as the development process progresses. Also, I think this is not a pure java issue, and looking at it from the whole Apache might help (as the web sites and the project documents would also need translation effort). I think a project which would take care of document and/or Resource bundle translation, coordinated with each Apache project requiring so would be a great thing in terms of infrastructure. I cc: community for insight, since there is much more in Apache than jakarta (even in the java world, there is a lot of XML people working in java) Regards -- Santiago Gala High Sierra Technology, S.L. (http://hisitech.com) http://memojo.com?page=SantiagoGalaBlog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: [Fwd: [vote] XMLBeans to enter XML incubation [was: Re:Vote for XMLBeans proposal in the XML Project (was RE: Vote for XMLBeansproposal)]]]
Steven Noels wrote: Dear Forrest committer, the current xml.apache.org charter requires a majority vote by all xml committers to adopt the proposal underneath. Could you please judge vote, preferably on [EMAIL PROTECTED] snip/ --- vote ballot -- Name: Marc Portier [+1] I agree with and support this proposal (+1) [ ] Indifference (-1 x +1) [ ] I object and suggest a way to address my reservations (-1) -- -marc= -- Marc Portierhttp://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center Read my weblog at http://radio.weblogs.com/0116284/ [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XML Beans advertised on Jakarta ... Re: Vote for XMLBeans proposal
On Wednesday, July 9, 2003, at 03:01 PM, Andrew C. Oliver wrote: On 7/7/03 2:09 PM, robert burrell donkin [EMAIL PROTECTED] wrote: XMLBeans feels (to me) like a jakarta component but if xml are happy to manage it, i'd say that it'd probably work out easier that way. there isn' t any reason why XMLBeans couldn't be visible on the jakarta website and as part of the jakarta community (which seem to be the main advantages which components see in joining jakarta) whilst being managed by the xml pmc (which would host their site and primary link). I'd object to that personally. We link projects which were in Jakarta historically and have become top level projects, but we do not link all of the XML projects. I'd object to that not only on practical concerns but with the logic Then I'd like POI linked from the XML site ;-) why shouldn't POI be linked from the XML site as well as the jakarta one? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XML Beans advertised on Jakarta ... Re: Vote for XMLBeansproposal
On 7/9/03 1:49 PM, robert burrell donkin [EMAIL PROTECTED] wrote: I'd object to that personally. We link projects which were in Jakarta historically and have become top level projects, but we do not link all of the XML projects. I'd object to that not only on practical concerns but with the logic Then I'd like POI linked from the XML site ;-) why shouldn't POI be linked from the XML site as well as the jakarta one? Maybe because its not an XML project under the XML PMC and has never been such? Maybe because the leftnav would get very long if every project on Apache was listed on the every other one? Though its fine with me... ;-) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
