User: jpmcc Date: 2008-06-13 05:59:58+0000 Modified: native-lang/www/planet/atom.xml native-lang/www/planet/index.html native-lang/www/planet/opml.xml native-lang/www/planet/rss10.xml native-lang/www/planet/rss20.xml
Log: Planet run at Fri Jun 13 07:00:28 BST 2008 File Changes: Directory: /native-lang/www/planet/ =================================== File [changed]: atom.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/atom.xml?r1=1.354&r2=1.355 Delta lines: +62 -42 --------------------- --- atom.xml 2008-06-13 00:00:03+0000 1.354 +++ atom.xml 2008-06-13 05:59:55+0000 1.355 @@ -5,9 +5,67 @@ <link rel="self" href="http://native-lang.openoffice.org/planet/atom.xml"/> <link href="http://native-lang.openoffice.org/planet/"/> <id>http://native-lang.openoffice.org/planet/atom.xml</id> - <updated>2008-06-13T00:00:38+00:00</updated> + <updated>2008-06-13T06:00:31+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> + <entry xml:lang="utf-8"> + <title type="html">Community Forum Japanese Opens on June 12, 2008</title> + <link href="http://openoffice.exblog.jp/7206499/"/> + <id>http://openoffice.exblog.jp/7206499/</id> + <updated>2008-06-13T02:17:48+00:00</updated> + <content type="html">"I am very pleased with this announcement. I encourage all Japanese speaking Community members to become involved with the Forum so it becomes an essential resource for our Native Language Community" said Maho Nakata, the OpenOffice.org Japanese Native-Language Project Lead.<br /> +<br /> +It was on Wed, 28 Nov 2007, the OpenOffice.org® Community announced the OpenOffice.org Community Forum.<br /> +<br /> +On Thu, 12 Jun 2008, the OpenOffice.org® Community announced the addition of Japanese language support to its Users' Community Forum. It was also released as a Press Release at prweb.<br /> +<br /> +Have you visited OpenOffice.org Community Forums?<br /> +<br /> +Currently OpenOffice.org User Community Forum supports four languages.<br /> +<br /> +Community forum, English<br /> +Communauté francophone, French<br /> +Közösségi fórum, Hungarian<br /> +ã³ãã¥ããã£ã¼ãã©ã¼ã©ã , Japanese<br /> +<br /> +Setting up of the Community Forum Japanese was initiated by OUCV around May 18th.<br /> +<br /> +What a speed! It is less than four weeks from the initiation to the go-live with the announcements including Japanese announcement.<br /> +<br /> +If you like to add your language support to OpenOffice.org Community Forum, go get ask OUCV. :)<br /> +<br /> +Here are some info about the Community Forum Japanese.<br /> +<br /> +- Managed by OUCV<br /> +<br /> +<br /> +- Powered by phpBB<br /> +<br /> +<br /> +- Translated to Japanese principally by ocean<br /> +<br /> +- Important: By any use of the Website, you agree to be bound by the Policies and Terms of Use<br /> +<br /> +- Hosted by Sun Microsystems<br /> +<br /> +<br /> +- Powered by PostgreSQL<br /> +<br /> +<br /> +"The OpenOffice.org Users' Community Forum covers the globe, and brings together experts and novices to provide a level of quality support that money literally can't buy," said Drew Jensen, one of the Forum administrators. "People appreciate that the Community has given them this world class software for free. Helping others via the Forum is one way to give something back."<br /></content> + <author> + <name>khparametric</name> + <uri>http://openoffice.exblog.jp</uri> + </author> + <source> + <title type="html">Hirano, Kazunari</title> + <subtitle type="html">Hirano, Kazunari</subtitle> + <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> + <id>http://openoffice.exblog.jp/atom.xml</id> + <updated>2008-06-13T06:00:30+00:00</updated> + </source> + </entry> + <entry> <title type="html">Better late than ...</title> <link href="http://lodahl.blogspot.com/2008/06/better-late-than.html"/> @@ -168,7 +226,7 @@ <subtitle type="html">Hirano, Kazunari</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2008-06-13T00:00:37+00:00</updated> + <updated>2008-06-13T06:00:30+00:00</updated> </source> </entry> @@ -225,7 +283,7 @@ <subtitle type="html">Hirano, Kazunari</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2008-06-13T00:00:37+00:00</updated> + <updated>2008-06-13T06:00:30+00:00</updated> </source> </entry> @@ -367,7 +425,7 @@ <subtitle type="html">Hirano, Kazunari</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2008-06-13T00:00:37+00:00</updated> + <updated>2008-06-13T06:00:30+00:00</updated> </source> </entry> @@ -517,42 +575,4 @@ </source> </entry> - <entry xml:lang="en"> - <title type="html">How to urinate on a violin</title> - <link href="http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/"/> - <id>http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/</id> - <updated>2008-05-23T15:50:20+00:00</updated> - <content type="html"><p>The story of OOXML and in general the story of proprietary formats and protocols being used and promoted to control the market and the access of citizens to digital re <span lang="en-US">sources is a long but fascinating one. The three (yes, three) last episodes of the OOXML story are a good example of that.</span> -<p lang="en-US">Ever since Wednesday night, three important news were announced. Let me comment each of them as briefly as I can.</p> -<p lang="en-US"> </p> -<ul> -<li> <span lang="en-US">Microsoft will not support the ISO standard sometimes referred to as OOXML in its current set of office solutions, Microsoft Office 2007 and 2008 (for Macs). The formats used by Microsoft are also called OOXML, but they are not the same as the ISO/IEC 29500 standard. Confusing? Hmm, yes. That one, about which we know very few besides that the ITTF refuses to share it with the world, will be implemented by MS Office 14, the next version Office around 2010 or 2011.</span> <span lang="en-US"><em>And me who thinks there were hundreds of OOXML implementations? Where are they? Gone, gone, gone, with the wind, just like the Old South of Scarlet O&#8217;Hara, a fantasy of past times, which OOXML today turns out to be.</em></span></li> -<li> <span lang="en-US">I willingly put the news item on the lack of support of OOXML by Microsoft Office 2007 first, because I get the feeling that these are the most important news here. But if you</span> <a href="http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx"><span lang="en-US">check the source</span></a> <span lang="en-US">, you will also see the other very important news item: Microsoft will integrate the native support of ODF in Microsoft Office 2007. This calls for several comments. First, what Microsoft will do exactly is left to be seen. We are told that the ODF support will come with the Office 2007 Service Pack 2 that will be released in 2009. That&#8217;s a long time before the market can benefit from ODF in Microsoft products. Perhaps more disturbingly, Microsoft announces the support for ODF 1.1. I understand that&#8217;s the majority of the ODF documents out there, and I would understand this as being a very pragmatic choice if its support was not scheduled in 2009, that is, months and months after ODF 1.2 will be released (at least as definite specification). That is something I have trouble understanding. The second question I have is what kind of native support we&#8217;re talking about. I am inclined to think that we might have an actual quality support of ODF in Microsoft Office, but integrating a converter such as the existing ones or providing lousy support -on purpose- will not do the job. The market wants real, native, effective support of ODF (real-world version) in MS Office as soon as possible and with no strings attached. All things considered, I do however genuinely applaud Microsoft&#8217;s move and find it useful and welcome</span> <span lang="en-US"><em>provided that no games are played and transparency and openness are respected.</em></span></li> -<li> <span lang="en-US">Microsoft is also announcing its participation to the OASIS ODF Technical Committee. One less well contemplated element in this news is that Microsoft announces that their OSP (Open Specification Promise) will cover ODF. I don&#8217;t know what to think about it at this stage, so my opinion will be transitional (no pun intended here). I am not sure how useful this is, as the OSP</span> <a href="http://www.grokdoc.net/index.php/EOOXML_objections#Patent_rights_to_implement_the_Ecma_376_specification_have_not_been_granted"><span lang="en-US">conveys no rights</span></a> <span lang="en-US">and is notably unsafe for Free Software implementations, dixit the Software Freedom Law Center. In short, I don&#8217;t like that announcement about the OSP. It smells bad, or at the very least dubious. In the same train of thoughts, I believe the OASIS should be wary of what Microsoft really wants to do inside the ODF TC. But here again, I am applauding the move by Microsoft, although I suspect them of having ulterior motives.</span></li> -<li> <span lang="en-US">Last but not least, the South African Bureau of Standards (SABS)</span> <a href="http://www.openmalaysiablog.com/2008/05/the-south-afric.html"><span lang="en-US">has filed an appeal to the ISO/IEC today against OOXML</span></a> <span lang="en-US">. This is an important decision. I believe that the whole OOXML standardization process has turned into a farce, and many think the same. Perhaps the ISO will deem this appeal receivable, unless their strange world-logic will make them feel offended by this request. In short, the latest announcements should not all of a sudden redeem Microsoft for what they did to the standardization, the industry, and the citizens at large. The software vendor has actually managed to destroy trust of many people, including the European Commission, who now wants</span> <a href="http://www.vnunet.com/itweek/news/2217375/ec-investigate-microsoft-odf"><span lang="en-US">to check how well Microsoft will play with ODF</span></a> <span lang="en-US">. Old world&#8217;s paranoïa? No. But somebody&#8217;s got to do something about it, somehow.</span></li> -</ul> -<p lang="en-US">The points above call for some closing comments. How will this affect the industry? It is too early to tell, and besides, these are just announcements. We will see what kind of beef will be served later on. On the front of open standards, this could be a moderate success. If Microsoft walks the line, we will see an expansion of interoperability across the industry, the users and the vendors; but we&#8217;re still waiting for Microsoft Office to use ODF by default.</p> -<p lang="en-US"> </p> -<p> <span lang="en-US">In the end, this will have been a tremendous waste of time. I&#8217;m sure that Microsoft will try to gain some advantage from OOXML, as broken as it is. They could try to reproduce what they managed to do with .NET and CLR by standardizing and opening only a subset of the .Net API , thus letting Novell create a very limited .Net implementation, Mono. Regardless of what the future options could be, the OOXML standardization will prove to be the single most destructive episode of the standardization history. No other standard will have been paid so dearly to achieve so few, while in the real world, the unspecified file format called OOXML and used by Microsoft Office 2007 will continue to lock in generations of users; <a href="http://news.cnet.com/8301-13505_3-9949736-16.html">Sharepoint will not stop using OOXML,</a> as Matt Asay points out. All this, to put it to rest, begs one and final comment, led to nothing more than what we had start off with: a real open standard (ODF), a proprietary format, and the vague premise of an ISO standard. Urinating on a violin would not have taken us any further.</span> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p><br clear="left" /></p> -<p class="akst_link"><a href="http://standardsandfreedom.net/?p=69&akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_69" class="akst_share_link" rel="nofollow">Share This</a> -</p></p></p></content> - <author> - <name>Charles Schulz</name> - <uri>http://standardsandfreedom.net</uri> - </author> - <source> - <title type="html">Moved by Freedom - Powered by Standards » OOo Postings</title> - <subtitle type="html">A weblog by Charles-H. Schulz.</subtitle> - <link rel="self" href="http://standardsandfreedom.net/index.php/category/ooo-postings/feed"/> - <id>http://standardsandfreedom.net/index.php/category/ooo-postings/feed</id> - <updated>2008-06-09T12:00:41+00:00</updated> - </source> - </entry> - </feed> File [changed]: index.html Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/index.html?r1=1.354&r2=1.355 Delta lines: +55 -35 --------------------- --- index.html 2008-06-13 00:00:03+0000 1.354 +++ index.html 2008-06-13 05:59:55+0000 1.355 @@ -28,8 +28,62 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 13, 2008 12:00 AM GMT</em></p> +<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 13, 2008 06:00 AM GMT</em></p> +<h2>June 13, 2008</h2> +<h3> +<a href="http://openoffice.exblog.jp"; title="Hirano, Kazunari"> +Kazunari Hirano</a> : +<a href="http://openoffice.exblog.jp/7206499/";> +Community Forum Japanese Opens on June 12, 2008</a> +</h3> +<p> +"I am very pleased with this announcement. I encourage all Japanese speaking Community members to become involved with the Forum so it becomes an essential resource for our Native Language Community" said Maho Nakata, the OpenOffice.org Japanese Native-Language Project Lead.<br /> +<br /> +It was on Wed, 28 Nov 2007, the OpenOffice.org® Community announced the OpenOffice.org Community Forum.<br /> +<br /> +On Thu, 12 Jun 2008, the OpenOffice.org® Community announced the addition of Japanese language support to its Users' Community Forum. It was also released as a Press Release at prweb.<br /> +<br /> +Have you visited OpenOffice.org Community Forums?<br /> +<br /> +Currently OpenOffice.org User Community Forum supports four languages.<br /> +<br /> +Community forum, English<br /> +Communauté francophone, French<br /> +Közösségi fórum, Hungarian<br /> +ã³ãã¥ããã£ã¼ãã©ã¼ã©ã , Japanese<br /> +<br /> +Setting up of the Community Forum Japanese was initiated by OUCV around May 18th.<br /> +<br /> +What a speed! It is less than four weeks from the initiation to the go-live with the announcements including Japanese announcement.<br /> +<br /> +If you like to add your language support to OpenOffice.org Community Forum, go get ask OUCV. :)<br /> +<br /> +Here are some info about the Community Forum Japanese.<br /> +<br /> +- Managed by OUCV<br /> +<br /> +<br /> +- Powered by phpBB<br /> +<br /> +<br /> +- Translated to Japanese principally by ocean<br /> +<br /> +- Important: By any use of the Website, you agree to be bound by the Policies and Terms of Use<br /> +<br /> +- Hosted by Sun Microsystems<br /> +<br /> +<br /> +- Powered by PostgreSQL<br /> +<br /> +<br /> +"The OpenOffice.org Users' Community Forum covers the globe, and brings together experts and novices to provide a level of quality support that money literally can't buy," said Drew Jensen, one of the Forum administrators. "People appreciate that the Community has given them this world class software for free. Helping others via the Forum is one way to give something back."<br /></p> +<p> +<em><a href="http://openoffice.exblog.jp/7206499/";>by khparametric at June 13, 2008 02:17 AM GMT</a></em> +</p> +<br /> +<hr /> +<br /> <h2>June 11, 2008</h2> <h3> <a href="http://lodahl.blogspot.com/"; title="Lodahl's blog"> @@ -460,40 +514,6 @@ <br /> <hr /> <br /> -<h2>May 23, 2008</h2> -<h3> -<a href="http://standardsandfreedom.net"; title="Moved by Freedom - Powered by Standards » OOo Postings"> -Charles Schulz</a> : -<a href="http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/";> -How to urinate on a violin</a> -</h3> -<p> -<p>The story of OOXML and in general the story of proprietary formats and protocols being used and promoted to control the market and the access of citizens to digital re <span lang="en-US">sources is a long but fascinating one. The three (yes, three) last episodes of the OOXML story are a good example of that.</span> -<p lang="en-US">Ever since Wednesday night, three important news were announced. Let me comment each of them as briefly as I can.</p> -<p lang="en-US"> </p> -<ul> -<li> <span lang="en-US">Microsoft will not support the ISO standard sometimes referred to as OOXML in its current set of office solutions, Microsoft Office 2007 and 2008 (for Macs). The formats used by Microsoft are also called OOXML, but they are not the same as the ISO/IEC 29500 standard. Confusing? Hmm, yes. That one, about which we know very few besides that the ITTF refuses to share it with the world, will be implemented by MS Office 14, the next version Office around 2010 or 2011.</span> <span lang="en-US"><em>And me who thinks there were hundreds of OOXML implementations? Where are they? Gone, gone, gone, with the wind, just like the Old South of Scarlet O’Hara, a fantasy of past times, which OOXML today turns out to be.</em></span></li> -<li> <span lang="en-US">I willingly put the news item on the lack of support of OOXML by Microsoft Office 2007 first, because I get the feeling that these are the most important news here. But if you</span> <a href="http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx";><span lang="en-US">check the source</span></a> <span lang="en-US">, you will also see the other very important news item: Microsoft will integrate the native support of ODF in Microsoft Office 2007. This calls for several comments. First, what Microsoft will do exactly is left to be seen. We are told that the ODF support will come with the Office 2007 Service Pack 2 that will be released in 2009. That’s a long time before the market can benefit from ODF in Microsoft products. Perhaps more disturbingly, Microsoft announces the support for ODF 1.1. I understand that’s the majority of the ODF documents out there, and I would understand this as being a very pragmatic choice if its support was not scheduled in 2009, that is, months and months after ODF 1.2 will be released (at least as definite specification). That is something I have trouble understanding. The second question I have is what kind of native support we’re talking about. I am inclined to think that we might have an actual quality support of ODF in Microsoft Office, but integrating a converter such as the existing ones or providing lousy support -on purpose- will not do the job. The market wants real, native, effective support of ODF (real-world version) in MS Office as soon as possible and with no strings attached. All things considered, I do however genuinely applaud Microsoft’s move and find it useful and welcome</span> <span lang="en-US"><em>provided that no games are played and transparency and openness are respected.</em></span></li> -<li> <span lang="en-US">Microsoft is also announcing its participation to the OASIS ODF Technical Committee. One less well contemplated element in this news is that Microsoft announces that their OSP (Open Specification Promise) will cover ODF. I don’t know what to think about it at this stage, so my opinion will be transitional (no pun intended here). I am not sure how useful this is, as the OSP</span> <a href="http://www.grokdoc.net/index.php/EOOXML_objections#Patent_rights_to_implement_the_Ecma_376_specification_have_not_been_granted";><span lang="en-US">conveys no rights</span></a> <span lang="en-US">and is notably unsafe for Free Software implementations, dixit the Software Freedom Law Center. In short, I don’t like that announcement about the OSP. It smells bad, or at the very least dubious. In the same train of thoughts, I believe the OASIS should be wary of what Microsoft really wants to do inside the ODF TC. But here again, I am applauding the move by Microsoft, although I suspect them of having ulterior motives.</span></li> -<li> <span lang="en-US">Last but not least, the South African Bureau of Standards (SABS)</span> <a href="http://www.openmalaysiablog.com/2008/05/the-south-afric.html";><span lang="en-US">has filed an appeal to the ISO/IEC today against OOXML</span></a> <span lang="en-US">. This is an important decision. I believe that the whole OOXML standardization process has turned into a farce, and many think the same. Perhaps the ISO will deem this appeal receivable, unless their strange world-logic will make them feel offended by this request. In short, the latest announcements should not all of a sudden redeem Microsoft for what they did to the standardization, the industry, and the citizens at large. The software vendor has actually managed to destroy trust of many people, including the European Commission, who now wants</span> <a href="http://www.vnunet.com/itweek/news/2217375/ec-investigate-microsoft-odf";><span lang="en-US">to check how well Microsoft will play with ODF</span></a> <span lang="en-US">. Old world’s paranoïa? No. But somebody’s got to do something about it, somehow.</span></li> -</ul> -<p lang="en-US">The points above call for some closing comments. How will this affect the industry? It is too early to tell, and besides, these are just announcements. We will see what kind of beef will be served later on. On the front of open standards, this could be a moderate success. If Microsoft walks the line, we will see an expansion of interoperability across the industry, the users and the vendors; but we’re still waiting for Microsoft Office to use ODF by default.</p> -<p lang="en-US"> </p> -<p> <span lang="en-US">In the end, this will have been a tremendous waste of time. I’m sure that Microsoft will try to gain some advantage from OOXML, as broken as it is. They could try to reproduce what they managed to do with .NET and CLR by standardizing and opening only a subset of the .Net API , thus letting Novell create a very limited .Net implementation, Mono. Regardless of what the future options could be, the OOXML standardization will prove to be the single most destructive episode of the standardization history. No other standard will have been paid so dearly to achieve so few, while in the real world, the unspecified file format called OOXML and used by Microsoft Office 2007 will continue to lock in generations of users; <a href="http://news.cnet.com/8301-13505_3-9949736-16.html";>Sharepoint will not stop using OOXML,</a> as Matt Asay points out. All this, to put it to rest, begs one and final comment, led to nothing more than what we had start off with: a real open standard (ODF), a proprietary format, and the vague premise of an ISO standard. Urinating on a violin would not have taken us any further.</span> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p><br clear="left" /></p> -<p class="akst_link"><a href="http://standardsandfreedom.net/?p=69&akst_action=share-this"; title="E-mail this, post to del.icio.us, etc." id="akst_link_69" class="akst_share_link" rel="nofollow">Share This</a> -</p></p></p></p> -<p> -<em><a href="http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/";>by Charles at May 23, 2008 03:50 PM GMT</a></em> -</p> -<br /> -<hr /> -<br /> <a id="disclaimer" name="disclaimer"></a> <p><em>Disclaimer: all views expressed on this page are those of the individual contributors, and may not reflect the views of the File [changed]: opml.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/opml.xml?r1=1.354&r2=1.355 Delta lines: +1 -1 ------------------- --- opml.xml 2008-06-13 00:00:03+0000 1.354 +++ opml.xml 2008-06-13 05:59:55+0000 1.355 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Native Language Confederation Planet</title> - <dateModified>Fri, 13 Jun 2008 00:00:38 +0000</dateModified> + <dateModified>Fri, 13 Jun 2008 06:00:31 +0000</dateModified> <ownerName>Native Language Confederation</ownerName> <ownerEmail>[EMAIL PROTECTED]</ownerEmail> </head> File [changed]: rss10.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss10.xml?r1=1.83&r2=1.84 Delta lines: +47 -26 --------------------- --- rss10.xml 2008-06-12 00:00:00+0000 1.83 +++ rss10.xml 2008-06-13 05:59:55+0000 1.84 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="http://openoffice.exblog.jp/7206499/"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-7336252722835671090" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-4193864903664578342" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-3968515596015606633" /> @@ -32,11 +33,56 @@ <rdf:li rdf:resource="tag:sophiegautier.com,2008-05-25:/blog/73" /> <rdf:li rdf:resource="tag:sophiegautier.com,2008-05-25:/blog/72" /> <rdf:li rdf:resource="tag:sophiegautier.com,2008-05-24:/blog/71" /> - <rdf:li rdf:resource="http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/"; /> </rdf:Seq> </items> </channel> +<item rdf:about="http://openoffice.exblog.jp/7206499/";> + <title>Kazunari Hirano: Community Forum Japanese Opens on June 12, 2008</title> + <link>http://openoffice.exblog.jp/7206499/</link> + <content:encoded>"I am very pleased with this announcement. I encourage all Japanese speaking Community members to become involved with the Forum so it becomes an essential resource for our Native Language Community" said Maho Nakata, the OpenOffice.org Japanese Native-Language Project Lead.<br /> +<br /> +It was on Wed, 28 Nov 2007, the OpenOffice.org® Community announced the OpenOffice.org Community Forum.<br /> +<br /> +On Thu, 12 Jun 2008, the OpenOffice.org® Community announced the addition of Japanese language support to its Users' Community Forum. It was also released as a Press Release at prweb.<br /> +<br /> +Have you visited OpenOffice.org Community Forums?<br /> +<br /> +Currently OpenOffice.org User Community Forum supports four languages.<br /> +<br /> +Community forum, English<br /> +Communauté francophone, French<br /> +Közösségi fórum, Hungarian<br /> +ã³ãã¥ããã£ã¼ãã©ã¼ã©ã , Japanese<br /> +<br /> +Setting up of the Community Forum Japanese was initiated by OUCV around May 18th.<br /> +<br /> +What a speed! It is less than four weeks from the initiation to the go-live with the announcements including Japanese announcement.<br /> +<br /> +If you like to add your language support to OpenOffice.org Community Forum, go get ask OUCV. :)<br /> +<br /> +Here are some info about the Community Forum Japanese.<br /> +<br /> +- Managed by OUCV<br /> +<br /> +<br /> +- Powered by phpBB<br /> +<br /> +<br /> +- Translated to Japanese principally by ocean<br /> +<br /> +- Important: By any use of the Website, you agree to be bound by the Policies and Terms of Use<br /> +<br /> +- Hosted by Sun Microsystems<br /> +<br /> +<br /> +- Powered by PostgreSQL<br /> +<br /> +<br /> +"The OpenOffice.org Users' Community Forum covers the globe, and brings together experts and novices to provide a level of quality support that money literally can't buy," said Drew Jensen, one of the Forum administrators. "People appreciate that the Community has given them this world class software for free. Helping others via the Forum is one way to give something back."<br /></content:encoded> + <dc:date>2008-06-13T02:17:48+00:00</dc:date> + <dc:creator>khparametric</dc:creator> +</item> <item rdf:about="tag:blogger.com,1999:blog-5198340507565233169.post-7336252722835671090"> <title>Leif Lodahl: Better late than ...</title> <link>http://lodahl.blogspot.com/2008/06/better-late-than.html</link> @@ -318,30 +364,5 @@ <dc:date>2008-05-24T07:58:15+00:00</dc:date> <dc:creator>sophi</dc:creator> </item> -<item rdf:about="http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/";> - <title>Charles Schulz: How to urinate on a violin</title> - <link>http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/</link> - <content:encoded><p>The story of OOXML and in general the story of proprietary formats and protocols being used and promoted to control the market and the access of citizens to digital re <span lang="en-US">sources is a long but fascinating one. The three (yes, three) last episodes of the OOXML story are a good example of that.</span> -<p lang="en-US">Ever since Wednesday night, three important news were announced. Let me comment each of them as briefly as I can.</p> -<p lang="en-US"> </p> -<ul> -<li> <span lang="en-US">Microsoft will not support the ISO standard sometimes referred to as OOXML in its current set of office solutions, Microsoft Office 2007 and 2008 (for Macs). The formats used by Microsoft are also called OOXML, but they are not the same as the ISO/IEC 29500 standard. Confusing? Hmm, yes. That one, about which we know very few besides that the ITTF refuses to share it with the world, will be implemented by MS Office 14, the next version Office around 2010 or 2011.</span> <span lang="en-US"><em>And me who thinks there were hundreds of OOXML implementations? Where are they? Gone, gone, gone, with the wind, just like the Old South of Scarlet O&#8217;Hara, a fantasy of past times, which OOXML today turns out to be.</em></span></li> -<li> <span lang="en-US">I willingly put the news item on the lack of support of OOXML by Microsoft Office 2007 first, because I get the feeling that these are the most important news here. But if you</span> <a href="http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx"><span lang="en-US">check the source</span></a> <span lang="en-US">, you will also see the other very important news item: Microsoft will integrate the native support of ODF in Microsoft Office 2007. This calls for several comments. First, what Microsoft will do exactly is left to be seen. We are told that the ODF support will come with the Office 2007 Service Pack 2 that will be released in 2009. That&#8217;s a long time before the market can benefit from ODF in Microsoft products. Perhaps more disturbingly, Microsoft announces the support for ODF 1.1. I understand that&#8217;s the majority of the ODF documents out there, and I would understand this as being a very pragmatic choice if its support was not scheduled in 2009, that is, months and months after ODF 1.2 will be released (at least as definite specification). That is something I have trouble understanding. The second question I have is what kind of native support we&#8217;re talking about. I am inclined to think that we might have an actual quality support of ODF in Microsoft Office, but integrating a converter such as the existing ones or providing lousy support -on purpose- will not do the job. The market wants real, native, effective support of ODF (real-world version) in MS Office as soon as possible and with no strings attached. All things considered, I do however genuinely applaud Microsoft&#8217;s move and find it useful and welcome</span> <span lang="en-US"><em>provided that no games are played and transparency and openness are respected.</em></span></li> -<li> <span lang="en-US">Microsoft is also announcing its participation to the OASIS ODF Technical Committee. One less well contemplated element in this news is that Microsoft announces that their OSP (Open Specification Promise) will cover ODF. I don&#8217;t know what to think about it at this stage, so my opinion will be transitional (no pun intended here). I am not sure how useful this is, as the OSP</span> <a href="http://www.grokdoc.net/index.php/EOOXML_objections#Patent_rights_to_implement_the_Ecma_376_specification_have_not_been_granted"><span lang="en-US">conveys no rights</span></a> <span lang="en-US">and is notably unsafe for Free Software implementations, dixit the Software Freedom Law Center. In short, I don&#8217;t like that announcement about the OSP. It smells bad, or at the very least dubious. In the same train of thoughts, I believe the OASIS should be wary of what Microsoft really wants to do inside the ODF TC. But here again, I am applauding the move by Microsoft, although I suspect them of having ulterior motives.</span></li> -<li> <span lang="en-US">Last but not least, the South African Bureau of Standards (SABS)</span> <a href="http://www.openmalaysiablog.com/2008/05/the-south-afric.html"><span lang="en-US">has filed an appeal to the ISO/IEC today against OOXML</span></a> <span lang="en-US">. This is an important decision. I believe that the whole OOXML standardization process has turned into a farce, and many think the same. Perhaps the ISO will deem this appeal receivable, unless their strange world-logic will make them feel offended by this request. In short, the latest announcements should not all of a sudden redeem Microsoft for what they did to the standardization, the industry, and the citizens at large. The software vendor has actually managed to destroy trust of many people, including the European Commission, who now wants</span> <a href="http://www.vnunet.com/itweek/news/2217375/ec-investigate-microsoft-odf"><span lang="en-US">to check how well Microsoft will play with ODF</span></a> <span lang="en-US">. Old world&#8217;s paranoïa? No. But somebody&#8217;s got to do something about it, somehow.</span></li> -</ul> -<p lang="en-US">The points above call for some closing comments. How will this affect the industry? It is too early to tell, and besides, these are just announcements. We will see what kind of beef will be served later on. On the front of open standards, this could be a moderate success. If Microsoft walks the line, we will see an expansion of interoperability across the industry, the users and the vendors; but we&#8217;re still waiting for Microsoft Office to use ODF by default.</p> -<p lang="en-US"> </p> -<p> <span lang="en-US">In the end, this will have been a tremendous waste of time. I&#8217;m sure that Microsoft will try to gain some advantage from OOXML, as broken as it is. They could try to reproduce what they managed to do with .NET and CLR by standardizing and opening only a subset of the .Net API , thus letting Novell create a very limited .Net implementation, Mono. Regardless of what the future options could be, the OOXML standardization will prove to be the single most destructive episode of the standardization history. No other standard will have been paid so dearly to achieve so few, while in the real world, the unspecified file format called OOXML and used by Microsoft Office 2007 will continue to lock in generations of users; <a href="http://news.cnet.com/8301-13505_3-9949736-16.html">Sharepoint will not stop using OOXML,</a> as Matt Asay points out. All this, to put it to rest, begs one and final comment, led to nothing more than what we had start off with: a real open standard (ODF), a proprietary format, and the vague premise of an ISO standard. Urinating on a violin would not have taken us any further.</span> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p><br clear="left" /></p> -<p class="akst_link"><a href="http://standardsandfreedom.net/?p=69&akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_69" class="akst_share_link" rel="nofollow">Share This</a> -</p></p></p></content:encoded> - <dc:date>2008-05-23T15:50:20+00:00</dc:date> -</item> </rdf:RDF> File [changed]: rss20.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss20.xml?r1=1.84&r2=1.85 Delta lines: +46 -26 --------------------- --- rss20.xml 2008-06-12 00:00:00+0000 1.84 +++ rss20.xml 2008-06-13 05:59:55+0000 1.85 @@ -8,6 +8,52 @@ <description>Native Language Confederation Planet - http://native-lang.openoffice.org/planet/</description> <item> + <title>Kazunari Hirano: Community Forum Japanese Opens on June 12, 2008</title> + <guid>http://openoffice.exblog.jp/7206499/</guid> + <link>http://openoffice.exblog.jp/7206499/</link> + <description>"I am very pleased with this announcement. I encourage all Japanese speaking Community members to become involved with the Forum so it becomes an essential resource for our Native Language Community" said Maho Nakata, the OpenOffice.org Japanese Native-Language Project Lead.<br /> +<br /> +It was on Wed, 28 Nov 2007, the OpenOffice.org® Community announced the OpenOffice.org Community Forum.<br /> +<br /> +On Thu, 12 Jun 2008, the OpenOffice.org® Community announced the addition of Japanese language support to its Users' Community Forum. It was also released as a Press Release at prweb.<br /> +<br /> +Have you visited OpenOffice.org Community Forums?<br /> +<br /> +Currently OpenOffice.org User Community Forum supports four languages.<br /> +<br /> +Community forum, English<br /> +Communauté francophone, French<br /> +Közösségi fórum, Hungarian<br /> +ã³ãã¥ããã£ã¼ãã©ã¼ã©ã , Japanese<br /> +<br /> +Setting up of the Community Forum Japanese was initiated by OUCV around May 18th.<br /> +<br /> +What a speed! It is less than four weeks from the initiation to the go-live with the announcements including Japanese announcement.<br /> +<br /> +If you like to add your language support to OpenOffice.org Community Forum, go get ask OUCV. :)<br /> +<br /> +Here are some info about the Community Forum Japanese.<br /> +<br /> +- Managed by OUCV<br /> +<br /> +<br /> +- Powered by phpBB<br /> +<br /> +<br /> +- Translated to Japanese principally by ocean<br /> +<br /> +- Important: By any use of the Website, you agree to be bound by the Policies and Terms of Use<br /> +<br /> +- Hosted by Sun Microsystems<br /> +<br /> +<br /> +- Powered by PostgreSQL<br /> +<br /> +<br /> +"The OpenOffice.org Users' Community Forum covers the globe, and brings together experts and novices to provide a level of quality support that money literally can't buy," said Drew Jensen, one of the Forum administrators. "People appreciate that the Community has given them this world class software for free. Helping others via the Forum is one way to give something back."<br /></description> + <pubDate>Fri, 13 Jun 2008 02:17:48 +0000</pubDate> +</item> +<item> <title>Leif Lodahl: Better late than ...</title> <guid>tag:blogger.com,1999:blog-5198340507565233169.post-7336252722835671090</guid> <link>http://lodahl.blogspot.com/2008/06/better-late-than.html</link> @@ -299,32 +345,6 @@ <p>Bon c'était aussi l'occasion de revoir les anciens collègues de mon mari du carrefour numérique et cela m'a fait très plaisir de revoir Marc et Anne. Bonne continuation à tous les deux&nbsp;!</p></description> <pubDate>Sat, 24 May 2008 07:58:15 +0000</pubDate> </item> -<item> - <title>Charles Schulz: How to urinate on a violin</title> - <guid>http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/</guid> - <link>http://standardsandfreedom.net/index.php/2008/05/23/how-to-urinate-on-a-violin/</link> - <description><p>The story of OOXML and in general the story of proprietary formats and protocols being used and promoted to control the market and the access of citizens to digital re <span lang="en-US">sources is a long but fascinating one. The three (yes, three) last episodes of the OOXML story are a good example of that.</span> -<p lang="en-US">Ever since Wednesday night, three important news were announced. Let me comment each of them as briefly as I can.</p> -<p lang="en-US"> </p> -<ul> -<li> <span lang="en-US">Microsoft will not support the ISO standard sometimes referred to as OOXML in its current set of office solutions, Microsoft Office 2007 and 2008 (for Macs). The formats used by Microsoft are also called OOXML, but they are not the same as the ISO/IEC 29500 standard. Confusing? Hmm, yes. That one, about which we know very few besides that the ITTF refuses to share it with the world, will be implemented by MS Office 14, the next version Office around 2010 or 2011.</span> <span lang="en-US"><em>And me who thinks there were hundreds of OOXML implementations? Where are they? Gone, gone, gone, with the wind, just like the Old South of Scarlet O&#8217;Hara, a fantasy of past times, which OOXML today turns out to be.</em></span></li> -<li> <span lang="en-US">I willingly put the news item on the lack of support of OOXML by Microsoft Office 2007 first, because I get the feeling that these are the most important news here. But if you</span> <a href="http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx"><span lang="en-US">check the source</span></a> <span lang="en-US">, you will also see the other very important news item: Microsoft will integrate the native support of ODF in Microsoft Office 2007. This calls for several comments. First, what Microsoft will do exactly is left to be seen. We are told that the ODF support will come with the Office 2007 Service Pack 2 that will be released in 2009. That&#8217;s a long time before the market can benefit from ODF in Microsoft products. Perhaps more disturbingly, Microsoft announces the support for ODF 1.1. I understand that&#8217;s the majority of the ODF documents out there, and I would understand this as being a very pragmatic choice if its support was not scheduled in 2009, that is, months and months after ODF 1.2 will be released (at least as definite specification). That is something I have trouble understanding. The second question I have is what kind of native support we&#8217;re talking about. I am inclined to think that we might have an actual quality support of ODF in Microsoft Office, but integrating a converter such as the existing ones or providing lousy support -on purpose- will not do the job. The market wants real, native, effective support of ODF (real-world version) in MS Office as soon as possible and with no strings attached. All things considered, I do however genuinely applaud Microsoft&#8217;s move and find it useful and welcome</span> <span lang="en-US"><em>provided that no games are played and transparency and openness are respected.</em></span></li> -<li> <span lang="en-US">Microsoft is also announcing its participation to the OASIS ODF Technical Committee. One less well contemplated element in this news is that Microsoft announces that their OSP (Open Specification Promise) will cover ODF. I don&#8217;t know what to think about it at this stage, so my opinion will be transitional (no pun intended here). I am not sure how useful this is, as the OSP</span> <a href="http://www.grokdoc.net/index.php/EOOXML_objections#Patent_rights_to_implement_the_Ecma_376_specification_have_not_been_granted"><span lang="en-US">conveys no rights</span></a> <span lang="en-US">and is notably unsafe for Free Software implementations, dixit the Software Freedom Law Center. In short, I don&#8217;t like that announcement about the OSP. It smells bad, or at the very least dubious. In the same train of thoughts, I believe the OASIS should be wary of what Microsoft really wants to do inside the ODF TC. But here again, I am applauding the move by Microsoft, although I suspect them of having ulterior motives.</span></li> -<li> <span lang="en-US">Last but not least, the South African Bureau of Standards (SABS)</span> <a href="http://www.openmalaysiablog.com/2008/05/the-south-afric.html"><span lang="en-US">has filed an appeal to the ISO/IEC today against OOXML</span></a> <span lang="en-US">. This is an important decision. I believe that the whole OOXML standardization process has turned into a farce, and many think the same. Perhaps the ISO will deem this appeal receivable, unless their strange world-logic will make them feel offended by this request. In short, the latest announcements should not all of a sudden redeem Microsoft for what they did to the standardization, the industry, and the citizens at large. The software vendor has actually managed to destroy trust of many people, including the European Commission, who now wants</span> <a href="http://www.vnunet.com/itweek/news/2217375/ec-investigate-microsoft-odf"><span lang="en-US">to check how well Microsoft will play with ODF</span></a> <span lang="en-US">. Old world&#8217;s paranoïa? No. But somebody&#8217;s got to do something about it, somehow.</span></li> -</ul> -<p lang="en-US">The points above call for some closing comments. How will this affect the industry? It is too early to tell, and besides, these are just announcements. We will see what kind of beef will be served later on. On the front of open standards, this could be a moderate success. If Microsoft walks the line, we will see an expansion of interoperability across the industry, the users and the vendors; but we&#8217;re still waiting for Microsoft Office to use ODF by default.</p> -<p lang="en-US"> </p> -<p> <span lang="en-US">In the end, this will have been a tremendous waste of time. I&#8217;m sure that Microsoft will try to gain some advantage from OOXML, as broken as it is. They could try to reproduce what they managed to do with .NET and CLR by standardizing and opening only a subset of the .Net API , thus letting Novell create a very limited .Net implementation, Mono. Regardless of what the future options could be, the OOXML standardization will prove to be the single most destructive episode of the standardization history. No other standard will have been paid so dearly to achieve so few, while in the real world, the unspecified file format called OOXML and used by Microsoft Office 2007 will continue to lock in generations of users; <a href="http://news.cnet.com/8301-13505_3-9949736-16.html">Sharepoint will not stop using OOXML,</a> as Matt Asay points out. All this, to put it to rest, begs one and final comment, led to nothing more than what we had start off with: a real open standard (ODF), a proprietary format, and the vague premise of an ISO standard. Urinating on a violin would not have taken us any further.</span> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p lang="en-US"> </p> -<p><br clear="left" /></p> -<p class="akst_link"><a href="http://standardsandfreedom.net/?p=69&akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_69" class="akst_share_link" rel="nofollow">Share This</a> -</p></p></p></description> - <pubDate>Fri, 23 May 2008 15:50:20 +0000</pubDate> -</item> </channel> </rss> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
