木曜日 12 23, 2010

JTF Translation Festival 2010 - English as an official language in Japan

I joined JTF Translation Festival 2010 last week.  JTF stands for Japan Translation Federation, which consists of translation companies, client companies, and translators in Japan.  I have been joining this event as an audience, but this year, I spoke in one of the panel discussion and in the seminar about Machine Translation and Post Editing.  It was my first time to deliver such a presentation to professional translators, so I was so excited and very very happy.


First one was the discussion about "English as an official language in Japan - Is it realistic ?  How would it affect translation business ?".  The discussion followed the interesting presentation about India - the history and the latest trend of English as an official language in India".  It was presented by Doctor Giri (Yoshisato) Suzuki, Accosiate Professor at Taisho University.  It was really interesting to see now English is less and less popular in India.  The reason is the people who can read and write is increasing and the contents in Hindi are also increasing.  Hindi is one of the major languages spoken in India.  The key is, in India, English has been "official language" because of the the communication needs to balance the language variety.  Yes, that is the strong motivation.


Now looking at Japan, I have to admit we do not have enough motivation currently to use English.  So, the answer is No ? - to the question "English as an official language in Japan - Is it realistic ?".  I believe the answer is Yes, in the business field.  The reason why more companies chose English as the 1st language is not to make their employees good at speaking English, but to build the basics to hire more English-speaking people.  The purpose is to work with the world more dynamically. 


So, my answer is "Yes, we need English to work in the world".  Speaking English more often, I realized my communication style changes.  I used to keep quiet in public and ask questions personally after the presentation finishes.  I used to start with details and come to the conclusion at the end.  Now I do not hesitate to ask questions in public, and express the conclusion first or state the number of reasons first, such as "That's true.  There are 3 reasons.  They are...".  Whichever language we speak, such an open and clear communication style is important, I believe.  Speaking a specific language means sharing the culture that language is built with, to some extent.  Knowing different culture and sharing it with other countries' people is a benefit.  It will broaden our mind and reduce the worries.  


Suppose more and more companies use English as a second language in the daily work, what will happen to the translation industry ?  The translation market will shrink because they read, write, speak in English ?  My answer is No.  Do the professional translators translate the meeting materials, presentation slides, or email messages which are used in daily work ?  No.  They translate the documents or products which should be shared with customers of such a company.  Those products have to be translated as one of the localization process. 


Then, there is no change expected in the industry ?  ... No.  We should change the communication style like we speak in English.   With more communication done in English, the translators or translation company should change the style.  Rather than wait for direction, ask or suggest more pro-actively.  Use English to explain why you believe the source sentence includes an error.  Once you acquire different style, you can be very strong and unique.  That's because you can switch or balance the communication style.  For example, you can keep politeness which is a good part of Japanese, while you can show your enthusiasm and professionalism like you speak in English.  If you can do the both, you can be very unique and strong.


Well, I realized I wrote too much about the panel discussion.  But this is what I wanted to say if I had more time.  Let me talk about MT & Post Editing in the next entry.

水曜日 4 07, 2010

OSC 振り返りなど (Looking back OSC and others)

遅くなってしまいましたが、OSC の振り返りです。今回は金曜日しか出られなくて残念でした。当日は曇り〜雨で肌寒い日でした。自宅から会場までは、乗り換えいっぱいだけど静かな道中。田舎から田舎へ行くのって、遠いなぁ。駅に降りたら広大で綺麗な駅舎が... でも降りる人はまばら... 大学構内に入っても、人いないよ?... 会場どこ!? と不安はピークに。やっと見つけたホールの手前の階段のところに「オープンソースカンファレンス」と書いた黄色い旗が! 会場に入ると、そこはいつもより少しだけ静かな OSC でした。

会場の外側はさておき、中側は熱気でいっぱいの、いつもの OSC でした :-) !
いつものように展示を設置して、「一緒に翻訳しませんかー?」とお誘いしました。


フルサイズ

3 時からのセッションでは、「ありがとうから始めよう」のテーマで、初心者の方にもメッセージを伝えたいなぁ... と思っていましたが、最後に聞いてみたら、来て下さった方の 80% ほどは「翻訳しています」という方だったので、マーケティング失敗していましたね。。。すみません。最後の 20 分ほどは Q&A で「困っていること」について話し合いました。

フルサイズ

問題点は「用語や翻訳メモリーの共有が難しい」「英語と日本語を、常に一対一対応にして欲しいというクライアントからのリクエストに応えるのが難しい」「オープンソース製品を翻訳してもリアクションが少ない。モチベーションが保てない」などなど、色々ありました。とっても参考になりました。参加してくれたみなさん、ありがとうございました。

Q&A で話した内容や、それについて考えてみたことなど、また後日書いてみますね。

English:

With such a long blank, but let me write about Open Source Conference 2010 Spring in Tokyo. I joined only the first day, which was the shame, but had a wonderful time as always. The day started with a little rain and dark sky. I realized how long it will take to travel from country side to country side, instead of from country side to city area. Train rails are running like "hub and spoke", and when trying to reach the end of the spoke from another end of the spoke takes long long time. Well, I enjoyed changing trains and reading books or practicing my speech on the train, so it was good after all.

To be honest, after 1 hour and a half, I came to a little worry about my sense of direction... "is it right direction ? did I miss the station !?" Lucky enough, I arrived
at the station in time, but saw only a few people walking out from the train. Again, I came to worry "is there anyone coming to the event ? what should I do I have only 1 or 2 people coming to my booth or session..." So, I was so happy to find there were more people inside the building and though it is a little quieter than usual, there were a bunch of cool folks showing and talking over their favorite software actively.

I organized the desk and started to talk to them as usual "Why don't you join our translation activity ?" :-)

フルサイズ

From 3:15, I talked about "You can contribute to Open Source Software easily!". This time, I chose the main message as "If you do not have time or energy to contribute by transaltion or coding, let's say Thank You! to active contributors. That's one of the most effective ways to motivate them."

フルサイズ

I talked about my contribution to my local community - it's not Open Source Community but it is my "geographical" neighborhood. I started to clean up the garbage site which our neighbors use in common. I was so happy to see the site is cleaner than before and also happy to imagine the neighbors should be happy to. But after months, I came to a little tired. Maybe I was doing too much and exhausted. Then, one of the people who always passed by the site talked to me "Thank you very much for your work. I see you are working almost every day, and thanks to you, it is very clean and everybody is happy. Thank you so much. " Can you imagine how delighted I was !? Finally I realized it's not only me but many people enjoy the cleaner site and there are people who appreciate my work.

This can be said also to the OSS work. It is true people with high motivation work for themselves, but it is also true the appreciation from users who benefit from their work makes the energy to double or almost 10 times. It's easy - just say "Thank you" anywhere by emails, blogs, twitters... that's can be the source of energy.

Oh, I realized I wrote too much in English section - a few paragraphs were not written in Japanese section. Sorry.

In the talk session, there were many wonderful discussion. I will write them later in this blog. Cheers!

木曜日 2 25, 2010

OSC での発表資料 (SC presentation slides )

12 月に書いたブログを読み直したんですが、「すぐそこだけど、とっても遠い」と言っていましたね。もう明日になっちゃいましたよ。

12 月のわたしからの手紙を読むような気持ちです。あのころは不安でいっぱいでした。いや、今も不安はあるけれど、だいぶ開き直ってきた感じ。わからないことは勇気を出して聞く、回答が得られなかったらもう一度自分で考えてみる、それでも結論が出ないときは、自分なりの目標を決めて、そこに向かって突っ走る、これでがんばっています。今は「そこに向かって突っ走る」ステップかな。。。

明日のセミナーで使うスライドがやっとできたので、アップします。

今回は原点に戻って、翻訳による OSS (Open Source Software) への貢献の大切さを話したいと思っています。スライド枚数多くなっちゃったんですが、早口にならないように気をつけますわー。場所が大学キャンパスなので、学生さんが多いのかしら。。。雨が降りませんように。。。

English:


I was reading my blog in December. I said "February is soon, but very far."... now it's tomorrow! I will talk at Open Source Conference 2010 Tokyo/Spring tomorrow.

It's like I am reading a letter from myself in the past. I was uncertain for many things and worrying too much. Now 2 months later, still uncertainty is there, but I feel more comfortable and confident with my goals. I have been trying to run the following steps: 1. Think positive and creative, 2. Take courage to ask anythingI do not understand, 3. If no answer is provided, think again in my own way, 4. If I cannot reach the conclusion, create my own goals, and 5. Run for it. I am now on Step 5.

Finally, I finished my slides for tomorrow's talk. Here you go!

This time, I come back to the origin of my activity, and talk about how important the translation is, and how valuable it is as a contribution to Open Source Software (OSS). I want to say so much, and the slides are 46 pages... hummm, I will try not to speak too fast. It's college campus where OSC is hosted this time - I may be able to see more students than usual. Hope it is not raining tomorrow ;-)

水曜日 2 24, 2010

Open Source Conference 2010 Tokyo/Spring is coming!

こんにちは!1 月からずっと落ち着かない日々でしたが、その間も仕事がんばっていました。SunGloss が Read Only モードになって、Terminology Database というシステムに移行しました。そのための枠組みや仕組みを作っていたのです。

SunGloss の欠点は、翻訳中に「これ訳すの?」と思ったら、手で用語を入力して検索しないといけないことでした。「もう知ってるからいいわ」とか、そもそも用語登録されていることに気づかないで、違う訳を付けてしまうという問題がよくありました。

そこで、社内でも使っている Terminology Database という仕組みをオープンにできないかと考えていたのです。プラハのエンジニア、サンのランゲージリード (x 9 言語)、プログラムマネージャーと相談しながら進めていたプロジェクトが、やっと完成しました〜!

OpenCTI インタフェースの Terminology タブからアクセスできます。このタブの使い方も含め、OpenCTI の機能を Open Source Conference 2010 Tokyo/Spring で紹介します。

セミナーは 2/26 金曜日の 15:15 からです。今回は、シンプルに「一緒に翻訳しませんか?」というメッセージでお話させていただきます。「自分には大したことはできないから...」「時間ないし...」と思っている方、いえいえ、あります!すぐに貢献できる方法が。詳しくはセミナーで!

English:
Hello! Long time no see :-) There have been so many things to work on since the beginning of this year, so I have been working on many different tasks. One example is OpenSolaris 2010.03 message translation, and another is SunGloss migration to Terminology Database. Now SunGloss is read-only mode and any new update will be made to Terminology Database. I have been building the framework and designing the interface with my trusted peer, Lukas, in Prague.

One of the major disadvantage SunGloss has is the lack of integration with translation tools. If a translator has to search SunGloss manually to find a term. It takes time to visit SunGloss, search for a term, and use that term in the translation. So, it often happens translators avoid using SunGloss sometimes because they thought they already knew the term, or sometimes because they do not know the term is registered. It often resulted in a wrong translation.

That's why we thought we may be able to open the terminology database system that we use internally to the translation community. I have been working with engineers in Prague, Sun's Language Leads (x 9 languages), and Program Managers... now it's done (or almost done)!

You can take a look of TD interface at Terminology tab on OpenCTI interface. I will talk about how to use this tab and other topics related to translation project at Open Source Conference 2010 Tokyo/Spring on Feb 26 Friday.

My seminar starts at 15:15 on Feb 26th Friday. This time, I will focus the simple message "Let's translate OSS. Yes, You can!". If you think "I cannot contribute anything..." or "I do not have time...", it's not true ;-) There are hundreds of ways to contribute to OSS. I can show you the easiest and simplest way, in addition to the translation. Looking forward to meeting you there!

木曜日 12 24, 2009

クリスマスイブだー (It's a Christmas Eve!)

今日は久しぶりに、なんでもない話をします。クリスマスイブですね。

わたしは、一年の中でこの季節が一番好きです。空気がつーんと冷たくてクリアで、すべてがよく見えて、そしてすべて新しくスタートできそうな気がして。

そこでちょっと哲学的な話を。

どんなことにも理由はあると思う。今住んでいる国、場所、家、仕事している環境、家族... 偶然だとか成り行きだとか、だから仕方ない、自分では変えられないって思っていることがいっぱいあるよね。でも、本当に変えられないのか?と、自分に聞いてみる。何度も何度も聞いてみる。すぐに答えが出ないときは、その問いを胸にとどめておいて、何か刺激があるたびに、問い直してみる。そして、変えられるものは変えていき、変えられないものは自分の中で整理して納得して前に進む。。。。今年は、そんな一年でした。

変えられるものを変える勇気、変えられないものを受け入れる力、そしてそれらを見分ける知恵 ... これは、わたしにとって永遠のテーマだと感じています。

たくさんの変化の中で、それらを追いかけているだけでは、いつも被害者になってしまうよね。でも、こんな場合はこうしようって作戦をたてて、自分が先頭にたっていけば、主導権を持つことができる。そう思って、いろんなことにチャレンジしてきました。でも、今年は自分の力では変えられないことが多かったーーー。。。(と思いませんか?)

とはいえ、その中でも、たくさんの作戦をたて、選択をしてきているのです。知らないうちに。今、ここにいてこのブログを書いていることも、わたしの選択。だから自信を持って進んでいこうと思います。来年も、がんばるぞー! Open Source Conference 2009 Tokyo/Spring にも、出るぞー! そのころの私は、どんなふうになっているでしょう。2 月末です。すぐそこだけど、とっても遠い。

ではみなさん、メリークリスマス!そしてよいお年を。来年もよろしくお願いします。

English:

I will not talk about Translation today, and talk about "nothing" but personal. It's a Christmas Eve today!

I like this season the best in a year. Very cold, clear air, and everybody looks happy. It makes me feel I can see everything clearly and I can start everything from a scratch in a new year.

I'll talk something spiritual today.

I believe everything has a reason to be there. Where we live, what we do for living, family, friends... everything seems to happen by coincidence or seems to be unavoidable. But I know there's a reason why we chose it. Yes, we chose it before or after we were born. We are making decisions while we are not aware.

I often ask myself "Is that what you want? If not, can you change it ?" I cannot answer sometime, then, keep that question in my mind and take any chance and ask again. If the answer is yes, I change it. If not, I manage myself to accept it. Never avoid looking at the fact, and try my best to deal with it. That's the way I lived this year.

Grace to accept with serenity the things that cannot be changed, courage to change the things that should be changed, and the wisdom to distinguish the one from the other - this is my life-time goal.

I want to find myself in the driving seat of my life. I may not be able to stop the big wave is coming, but I can prepare myself to live over the wave. I do not want to be a victim of the fate. ... but, this year, there has been too many changes and uncertainty that we cannot control... Don't you think !?

It's true we did not have much that we could change. But, we are making decisions in every minute, and we can change our decisions at any time. Like now, I am writing this blog here in my home office. This is the result of what I have been choosing this year. It's my work and life, and I am proud of it!

Now, let's keep going in the next year too. I do not know what happens to us, but I will join Open Source Conference Tokyo / Spring in February! ... February... only 2 months away, but sounds so distant! I want to write a letter to me in February. I want to ask a lot of questions, like what are you doing ? where are you located ? ... but in the end I will ask instead, "Is it what you want ? If not, can you change it ?"

I wish you all a happy holiday season! See you next year! ;-)

木曜日 12 03, 2009

QCD のギャップを埋めるには ? (How to fill in the gap in QCD?)

Continued from the previous entry.

Let's hear from 3 different parties about QCD gap:

Product Supplier: I am a project manager localizing software messages, help, and documents. The things I always feel frustrated are the turnaround time from the translation company. We have less management resource, and time and cost is the highest priority. Quality ? It has to be good by default. But today, our language specialist reported me "The translation quality is not good. UI messages used in Help do not match the software at all. You cannot release the product with this translation." I do not know why. Translation company did not claim the time or cost is not enough, but why they deliver such quality !?

Translation Company: I am a translation project manager. I communicate with Product Supplier and manages Translators. I do not understand why my customer is unhappy with our delivery. I did send the translated files in time / under budget. They should be aware if the time and cost is limited as such, we cannot keep the good quality. I thought it has already been agreed. Alas! I worked very hard and did everything I could to keep the quality in such a limited condition. Translators are complaining about such a short schedule, but I did my best!

Translator: I am a freelance translator. I am not happy with the work I did, but I have to finish it as soon as possible. Yes, I get paid, but still not happy. I wanted to do differently if I have more time. Today, my agent claimed the quality was not good enough. I know!!! But was it their request to finish translation soon !?

All of the three parties are not happy in this case. If they continue this, the relationship and business will be lost. Off course this is a fiction - my imaginary story. But let me talk about I what we can do differently, based on this story.

In this case, for Product Supplier, Time and Cost is the first priority. For Translation Company, Customer Satisfaction. For Translator, Quality. How can we fill in the gap ?

I believe "Communication" and "Looking at the bigger picture" helps us. All of the three parties seem to look at themselves only. All of the unhappy feeling is coming from their own needs. How about imagining the next steps in the workflow ? For example, Product Supplier should imagine how Translation Company asks Translator to do, and ask again themselves "did I explain enough what is the needs ?". Translation Company can confirm with Product Supplier, "I understand your priority is Cost and Schedule, but how you want us to keep the quality ? Is there anything you cannot miss in the quality even if Cost and Schedule is met ?". If Product Manager cannot answer, Translation Company can ask Language Specialist directly. Translator can imagine why Product Supplier wants this translation so quickly. Maybe the reason is... for that Product Supplier, without translation, the product cannot be released. It may be the case they will release the product translation with the minimum quality, and update the contents on demand.

Translator can view their role as a creator and communicator, instead of just one of the work resource in the lowest layer of the resource pyramid. It is often said Translator is a specialist with strong craftsmanship. It is true in a sense. But the craft, the product that Translator is creating is one of the important communication method. "Communication" changes its shape and style according to the needs of human being. We can count how many acronyms are created every year with increasing interests in those specific topics.

Talking about the documents and communication, more and more documents are based on wiki and update cycle is shortened. The definition of "Completeness" of the document may be different , compared in 10 years ago. I would not say, that's why you should not complain about the lower quality expectation. Instead, you can imagine why your client wants that way ? If you have any idea, you can try your best to meet their needs. If you think the quality needs more care, you can suggest RFE. That's the creator and communicator can do.

What I am doing myself to fill in this gap as Product Supplier and Language Specialist is as follows:


  • Clarify the quality expectation to Translation Company using Quality Model.

  • Communiate with project manager and see if any disclaimer should be applied to the lower quality score.

  • Encourage Translation Company to send queries before their final delivery using Query Tool

  • Send over-all quality feedback regularly to Translation Company.

  • Send specific comments about errors and how to improve the quality.

What I keep in mind in answering questions and sending comments about errors is "My job is Not to criticize them, but to support them to help us in turn." I am happen to be in this position, but in another occasion or time, I may wear a different hat. Who knows ? Fair and Open - these are two important keys to make the world different.

The bottom line is, I think it may change the picture if we keep Fairness and Openness in our mind and view the picture from the other's point of view. We cannot change the facts, economy regression, limited resource, time, and budget, but we can change our way of getting satisfaction. Let's do something differently, rather than expecting others to do so :-)

JTF 翻訳祭で思ったこと (Thought after JTF Translation Festival)

I joined the conference hosted by Japan Translation Federation on November 20th at Hacchobori in Tokyo. The event is called JTF Translation Festival, and the details were as follows: 19th JTF Translation Festival.

It's a shame they did not provide English translation for this event :-( Here is the outline by me:


  • Presentation 1: "What We Value Most for Translator and Translation company" by Kazuyuki Nakamura, WPTG-Japan Senior Language Specialist at Oracle

  • Presentation 2: "Issues We Face in Drastically Changing Industry" by Koji Inoguchi, Technical Writer/Translator, Executive Director at JTF

  • Panel Discussion on "Countermeasure to Recession in Translation Industry"

"We" in the Presentation 1 is Product Supplier, such as Oracle or Sun, while "We" in the Presentation 2 is Translation Company and Translator. As far as I understand, it is more like "Translator". Mr. Nakamura illustrated the gap in QCD (Quality, Cost, and Delivery) expectation among three parties, Product Supplier, Translation Company, and Translator. Oh, I am very familiar with this gap ... I understand the needs of each party. But sometimes I have to say "Please do anything you can to meet our schedule" or "Please keep the cost under control by all means". Thinking in Translator's shoes, I would feel so frustrated like "what is she thinking !? Does she really expect such a volume can be completed within such a limited time frame !?"... Now, let me discuss more about the gap in QCD in the next blog entry.

Mr. Inoguchi walked us through what Translators can do to settle the gap. As I wrote "settle", not "fill in", he suggested Translators to find the best partner for themselves, instead of doing everything they can do to meet the unreasonable customer requests. Junior translators should not focus on the speed. The speed should be improved only after they spent enough time to keep the good quality.

I cannot agree with Inoguchi-san more than that. It is totally different 1) an experienced translator puts higher priority to the speed while keeping the quality under control, and 2) a junior translator does anything possible to meet the schedule. The difference is whether or not the one knows what he/she did and did not. You finish your work, and feel you did everything you could do in this limited time. Now, can you summarize what to do to improve the quality if you have more time ? If you answer Yes, you are in 1) case. If not, 2) case. "Taking more time" cannot be an answer.

The summary list should not be the "disclaimer" telling what you cannot do because of the restriction. The list should be "RFE" (Request For Enhancement). You could suggest the customer "If you have more time or cost, it is highly recommended to shoot these problems. Here is how-to, and the expected time and cost." Then, you will have higher possibility to get another job :-)

Well, the entry is longer now, so let me write about how we can fill in the gap in QCD in the next entry.

月曜日 11 09, 2009

Open Source Conference 2009 Tokyo Fall Report レポート (Reporting on my OSC 2009 Tokyo Fall)

こんなに遅くなってしまって、恥ずかしいけど、OSC 2009 Tokyo Fall のことを書きます。(いや、色々あって... そのことは後で書きます)

蒲田の会場は、新しくて綺麗で清潔でした。スタッフのみなさんも優しくて感謝。

1 日目はセミナーはしなくて、一日、「l10n よろず相談」のコーナーにいました。椅子が二つにテーブル一つ、看板たててパネルをたてて、、、PC では OpenCTI/CTI や OmegaT、Pootle のデモをしました。「翻訳一緒にしませんか?」と笑顔で勧誘します。。。気のせいか前回より怪訝な顔をされる機会が減った感じが。よかった!みんなで翻訳って、以前より受け入れられつつあるかしら? 

二日目はセミナーがあったので、ちょっと緊張していました。自分の考えを自分の言葉で表現して、かつ、来てくれる方のニーズにも応えるようなものにしたいって思うと「大丈夫かなぁ」と不安がよぎります。昼休みに、ひとりでセットアップと練習してたら、LINBIT の Partner Relationship Manager で、一日目のオープニングトークをした Florian が「ハロー」と入ってきました。「いやー、緊張するわー」と話すと、「じゃあ、うまく話すコツを教えてあげよう」と、いくつかヒントを教えてくれました。しっかり立って声を前に響かせること、スライドより参加者の目を見ること、質問があったら繰り返して意味を確認すること、などなど。ふむふむ、どれも納得するわ。その通りできるかどうかは別として、、、でも頑張る!と気合いを入れました。

さて、いよいよセミナー。部屋はいっぱいになったので、たぶん 40 - 50 人ぐらい来てくれたのかな。ありがとうございました! Florian に教えてもらったとおりに、いっぱい息を吸い込んで大きな声で話しました。早口にならないように、一方通行にならないように、、、30 分ほどでスライド発表は終わり、残り 15 分ぐらいで質問を受けました。やったー、うまくいったー!!と終わり近くなって、マイクをしていなかったことに気づいてしまった! Florian には「マイクを有効に使うこと」って言われたのに。あかんやん、私。


プレゼン資料をアップしますね。英語と日本語、どちらも作りました。

セッションの合間に自分もあちこち回ってみました。やっぱり興味があるのは、翻訳関係です。Eclipse 翻訳で使い始めたという翻訳ツールが見たい!と思ってセッションにも出てみました。xliff ベースで翻訳して、翻訳メモリーを共有しつつ、用語も共有して、というシステム。OpenCTI と同じ発想ですね。やっぱり興味アルー。使ってみたいー。翻訳者募集の際には是非声をかけてくださいとお願いしておきました。

Ubuntu などの翻訳プロジェクトでは、何を使っているんだろう、と興味あります。今度機会があったらお話聞きたいなぁ。

English:

I feel so ashamed to post my report about OSC 2009 Tokyo Fall now, but let me try... (oh, many things have been happening... let me write about it later ...)

Event space in Kamata was brand new, clean, and beautiful! All of the staff members were so nice and kind - thank you so much!

1st day - no seminar for me. I sit all day in our corner "All Sorts of Consultation about Localization/Translation - Sun-related OSS / OmegaT project". 2 chairs, 1 table, 2 PCs (one for me, and one for JC), with panels. I ran a demo of Pootle and OpenCTI on my PC, and JC did OmegaT on his Mac. If someone is passing by, I take full of my courage, and ask "why don't you join our translation project ?" with a big smile :-) and give out a booklet "Sun Community Guidebook". As far as I remember, the number of people who looks surprised and annoyed, like "what is translation for OSS!?", becomes less and more people are interested in my talk. That's a great sign! I really hope "contribution by translation" is more popular in Japan.

2nd day - Seminar day for me. I has been nervous from the beginning. I like to talk and make a presentation, but sometimes feel so nervous that I have to express my thoughts clearly in my words, and have to meet the needs of the audience... I was setting up and doing a dryrun all alone in the seminar room, then, Mr. Florian Haas, Partner Relationship Manager from LINBIT, who made a wonderful opening speech on the 1st day came in to day Hi! I said "Oh, I am very nervous... Do you have any tips to share ?", then, he showed me some. Having a good posture, Taking a deep breath to keep a fresh air in your lungs, looking in the eyes of a few people, instead of reading the slides, and repeat the questions to share with other audience... Hummm what a great words of wisdom. Thank you Florian. I do not know if I can remember all, but I will try ...

Now, it's my seminar time. The room was full, so I guess 40 - 50 people came in.. Thank you!!! I did my best to talk clearly and slowly enough. I took 30 minutes for presentation and 15 minutes for Q&A. Closer to the end, I realized I forgot to use a microphone ... I might have been shouting... sorry Florian, you said "use your microphone effectively", but I failed to even use it...;-(


Here is my presentation slides in English and Japanese.

I have been around the corners in different rooms to see translation related projects. I wanted to see the translation systems for Eclipse, and attended that session. The translation editor will be available as open source and the system uses xliff format, leveraging translation memory and terminology database ... like OpenCTI. Wow, exciting, I want to try it ! So, asked them to let me know when the translation project is ready to go.

I wonder which editor, translation system, or project management method is used for other projects, such as Ubuntu ... I really want to discuss with them.

木曜日 10 29, 2009

Open Source Conference 2009 Tokyo Fall

いよいよ明日からです、Open Source Conference Tokyo 2009 Fall。明日は展示コーナーに一日います。明後日の土曜日 (1 時から) はセミナーをします。内容は、春にやったものの続き... といいながら、春の内容をここにアップしていないことに今更気づきました。遅い。すいません。

春のスライドを、今更ですがアップロードします。「一緒に翻訳しようよ」というお誘いです。

今回は、「一緒に翻訳しようよ、こんなに便利なものもあるよ。」です。そう、キーワードは「役に立つ」です。すぐに使えそうな、翻訳のコツやツールの紹介をします。

では、会場でお会いしましょう!

English:

Open Source Conference Tokyo 2009 Fall is coming... it's tomorrow! I will be hanging around there all day on Friday and Saturday. I will make a presentation on Saturday from 1pm. I will talk the extended version of what I talked in spring... and now I realized I have not uploaded my slides to this blog yet. Time flies... sorry.

Here are my presentation slides. The message was "Let's translate our software in a team!".

The message this time is "Let's translate together, you can use various resources at your hand!". So, the keyword is "Get Leverage". I will share the translation techniques and tools that you can use from tomorrow.

See you there!

木曜日 10 01, 2009

OpenOffice.org 3.2 翻訳スタート ! (OpenOffice.org 3.2 translation starts!)

OpenOffice.org 3.2 のメッセージとヘルプの翻訳がスタートしました!サンから各コミュニティーに、「翻訳する人いませんか?」と募集をします。それに答えて各言語のコミュニティーが自分たちのソフトウェアで表示されるインタフェースやヘルプの内容を翻訳する、というプロジェクトです。

この活動は、2.x の頃から始めたのですが、最近、日本語コミュニティーがとても活発になってきて大変うれしい!翻訳プロジェクトのリーダー久保田さんと、サンのプロジェクトマネージャー Rafaella と、相談しながらスタート準備をしていましたが、すでに 4 人も翻訳メンバーが集まっていて心強いです。しかし締め切りは 10 月 16 日。アグレッシブー。がんばっていきましょう!

http://wiki.services.openoffice.org/wiki/User:Takaya/Translating3.2

今回も使うツールは Pootle です。でも、実際に翻訳するのはオフラインがいいです。Pootle に全員でアクセスするとかなり時間が... でも PO フォーマットを壊してしまうのが怖いので、OmegaTPoEdit を使いたい。。。個人的には OmegaT が好き。わたしも翻訳に参加してみようかな? OmegaT は PO のサポートが改善されたそうです。以前は fuzzy match に対応していなかったので、せっかく fuzzy な翻訳が msgstr に含まれていても、認識してくれませんでした。今度の OmegaT は、JC によると、fuzzy 翻訳が TM に保存されるので翻訳時には参照できるというではありませんか。楽しみだー。

そうそう、OmegaT プロジェクトと合同で、また Open Source Conference に出展します。10/30, 31 開催で、わたしは 10/31 の 13:00 から、「オープンソースソフトウェアを日本語で使おう Part II - 実践編」というタイトルでセミナーもやります。今回は、より詳細な活動内容と、翻訳のヒント、失敗例、成功例など、実践的な内容をお話したいと思っています。

▼OSC2009 Tokyoトップページ

http://www.ospn.jp/osc2009-fall/

▼セミナープログラム

30日(金)

http://www.ospn.jp/osc2009-fall/modules/eventrsv/?id=1&noform=1

31日(土)

http://www.ospn.jp/osc2009-fall/modules/eventrsv/?id=2&noform=1

▼展示一覧

http://www.ospn.jp/osc2009-fall/modules/xfsection/article.php?articleid=1

進化した OmegaT の話も JC からプレゼンありますよ。個人的にも楽しみ。

しかしまだ、セミナー内容全然決めてないわ。。。どうしよう。こんなことが聞きたいっていうアイデアのある方、教えてください!!!

English:


We have just started OpenOffice.org 3.2 message and online-help translation project! This is the project in which Sun asks for community to translate OpenOffice.org together. Various language communities have been joining this activity and translate the user interface and help messages into their own languages.

This has been started since 2.x for Japanese, and now Japanese translation community is becoming more and more active... and I am delighted! Translation project lead, Takaya Kubota, Sun project manager, Rafaella, and I have been working together to kick off the JA translation activity. Now, already 4 members volunteered to join this work. That's very exciting. Dead line is October 16th ... very aggressive... but let's focus this work and get them done in time!

http://wiki.services.openoffice.org/wiki/User:Takaya/Translating3.2

Also this time, the tool we use is Pootle. But we encourage the translators to download the files and translate off-line. It is better both for performance and efficiency. To prevent corrupting the format, however, translation tools supporting translation memory, such as OmegaT or PoEdit is strongly recommended. Personally, I love OmegaT:-)。I may join this work as a translator, if I can. Good news for OmegaT is its "fuzzy match" support. It uses to have no support to fuzzy match in PO file, but this time, according to JC, fuzzy match translation can be referenced and leveraged by OmegaT TM (Translation Memory). I am looking forward to trying that feature myself.

Talking about OmegaT, I will host a corner at Open Source Conference with OmegaT project again. It will be on October 30 and 31. I will also deliver a seminar at 1pm on Oct. 31th, Saturday. The topic is "Let's use Open Source Software in your language Part II - Advanced". This time, I want to talk more about the examples - successful and not successful, and more tips for translation.

▼OSC2009 Tokyo Top page

http://www.ospn.jp/osc2009-fall/

▼Seminar Program

30th(Fri)

http://www.ospn.jp/osc2009-fall/modules/eventrsv/?id=1&noform=1

31st (Sat)

http://www.ospn.jp/osc2009-fall/modules/eventrsv/?id=2&noform=1

▼Pod List

http://www.ospn.jp/osc2009-fall/modules/xfsection/article.php?articleid=1

JC will talk about advanced OmegaT feature... I am happy to hear that personally.

But! I have not decided yet the detail of my seminar contents. Hummmm.... it's a big pressure. Anyone who has an idea or request, please let me know!!!

月曜日 9 14, 2009

CTI について (Introducing CTI)

こんにちは!久しぶりの更新です。いろんなことがありましたが、自分の志すところに変わりはないと再確認できましたので、また色々ここで情報発信していくことにしました。よろしくお願いします。

さて、今日は コミュニティー翻訳エディタ で簡単に紹介した Community Translation Editor (CTI) についてお話したいと思います。

CTI とは、一言でいえば、「Sun が使用している翻訳システムへのインタフェースとなる、ブラウザベースのエディタ」です。そこで何ができるかと言えば、「Sun の翻訳メモリーおよびシステムを活用した、コミュニティーによる翻訳」です。翻訳の流れには、おおまかに以下のステップがあります。

1) ファイルの準備

2) 過去の翻訳からの流用

3) 新規部分の翻訳

4) フォーマット (レイアウト確認)

5) 翻訳メモリーの作成と管理

これらのうち、3) の部分を行うのが CTI です。そして、残りのステップは Sun が担当します。作成された翻訳メモリーはエクスポートしてコミュニティーで保管する場合もあります。

CTI エディタでは、翻訳のセグメント (一区切り、ほとんどの場合は文章やタイトル、表内の一項目) ごとに日本語と英語が横にならんでいます。日本語の欄に翻訳を入れていけば翻訳は完成します。内部タグ (フォントやリンク) 以外は表示されないため、フォーマットを壊してしまう心配がありません。

これまで、わたしが関わっている翻訳プロジェクトでは、OpenSolaris.org の登録ページ翻訳で使いました。わたしが「必須」だと思っていた各種機能が入ったので、これからもっと使っていきたいなと思っています。

まだ開発途中のものなので、いっぱい希望はありますが、そられもかなりの数にのぼったため「どの機能が欲しいですか?」というアンケートを実施しています。
以下に CTI ブログ の記事を翻訳したものを記載しますので、よろしければご意見をお願いします!↓


CTI ブログ記事より (翻訳):

数ヶ月前、CTI チームからユーザーのみなさんに CTI ツール への要望 (Request for Enhancement、RFE) を募集しました。過去 6 ヶ月間に集まったご要望およびバグレポートは 50 件以上にのぼります。ありがとうございました。いただいたご要望は、 http://wikis.sun.com/display/g11n/CTI+RFEs.
にリストしています

今後、各案件に優先順位をつけて着手していきたいと考えていますが、その順位を特定するために、みなさんのご意見を聞かせてください。その手段として、CTI ツールに関する簡単なアンケートを用意しました。

情報を整理しやすくするため、類似性のある要望を 1 つのグループにまとめました。グループ分けは、http://wikis.sun.com/display/g11n/RFEs+Summary にリストしています。

アンケートの目的:


  1. CTI ツールのユーザー満足度を調査

  2. 投稿された要望の優先順位を特定

  3. CTI 開発作業への参加意志を確認 (バグ修正、機能改善など...)

アンケートには CTI ツールのメインページから、または a  アンケート から直接参加していただけます。アンケート期間は 9 月 4 日から 9 月 16 日までです。アンケートの結果は、後日 CTI Sun Wiki ページ で公開する予定です。

アンケートは 10 分以内で終わる簡単なもの です。アンケートに参加していただいた方の中から、抽選で 20 名 の方に、Sun オリジナル T シャツをプレゼントいたします

一人でも多くの方のご参加をお待ちしています!


English:


Hello! Long time no see! As you may know, there have been a lot of changes... but I re-confirmed my goal and dream has not changed at all, so let me restart my blog now. :-)

Today, I want to introduce one of the tools I wrote in Community Translation Editors, Community Translation Editor (CTI).

My definition of CTI in one word is... "Browser-based editor which interfaces between community users and Sun translation infrastructure", and what CIT can do is ... "Translation by community using Sun's translation memory and translation system." I would define the steps for translation using translation memory as follows:

1) Prepare files

2) Get leverage from the existing translation

3) Translate "new" (no leverage and fuzzy) part

4) Format (Confirm layout)

5) Create and maintain translation memory

Out of 5 steps, CTI supports Step 3), and the rest of 4 steps are done by Sun. Generated TM will be shared with community, and it can be maintained by community outside of Sun's system.

On CTI editor, the source and target segments are laid out side by side. Segments means a minimum translation unit, which is usually a sentence or words of title or table entity. Block tags which define the layout of the segments will not appear in the segment field, you do not have to worry about the risk of collapsing the layout.

I have used CTI for OpenSolaris.org registration page translation project, and it worked well. Also, the features I submitted as "mandatory" have now been implemented, so I am going to use CTI more actively for my projects.

CTI is still under the development, and I have many requests... but I know the resource is limited. Now I see the CTI team is running a survey to ask which feature you want the most. So, let's participate this survey and tell them what we want !! Here is the link to the survey and CTI blog entry↓


Blog Entry: http://blogs.sun.com/cti/entry/cti_tool_survey

The survey is accessible from the main page of the CTI tool or directly at a  Survey Tool.

火曜日 5 19, 2009

Joined and Talked at BarCamp

I joined Tokyo BarCamp on Saturday, May 15. Sun offered a place for this event, so I joined as a staff as well as a camper. It was my first time to even hear about this event. Jim let me know and Shoji asked for volunteers on our evangelist mail alias. So, at first, I thought I may be able to sit at the reception with a big smile, help someone if necessary, and leave there afternoon. But after all, I talked about "Translation Matters - Joy and Pain" in one of the morning sessions, attended and discussed at many sessions, talked a lot in the hallway, joined an interview and filmed, and promised with other female campers to do something to invite more women to such an event.

15-minute of sessions are so many and in a wide variety - some are very technical and some are more community-related. I mostly attended the less-tech sessions where we discussed the IT education, open communication, how we can get more female participants... I introduced what I am doing to evangelize translation activity, how it would be beneficial for both of contributors and the users to increase the volume of translated technical or informational documents on the web.

I know the issues are Glossary and Translation Memory management. Glossary can easily be the list of terms that translators do not know. They are not always the list of key terms, because they vary depending on the background and knowledge that the translators have. Translation Memory is good, but who and how to keep them updated and usable for the new translation ?

We started to use Community Translation Interface, and still keep updating the feature. I am also working on the SunGloss to sort out the terms more dynamically. Reduce the number of terms by eliminating the duplicated terms where only category or sub-category is different, move general terms from Product line to General, and merge per-language entry into one...

Well, it is now on the side track, but what I want to say today is BarCamp was so exciting and I was amazed, impressed and happy to meet so many enthusiastic and talented people there.





火曜日 4 28, 2009

Localization Matters (翻訳よもやま話)

I had a chance to share the localization issues with the editor team which provides the editorial services to the product writers. Those issues could be small, such as "missing space", or big and universal, such as "terminology management". I have been working to resolve this issue only on the translation side so far, and never had a chance to communicate with the writing team. So, I was delighted and excited about that chance. In my presentation, I introduced typical problems we face... those issues include the following:


As their names imply, these expressions <literal>try</literal> to execute some
code, but <literal>catch</literal> an exception if there is a problem.

This writer uses "try" and "catch" for two meanings by changing the type face to "literal" which is represented as courier font. In our standard typographic convention, courier font means the command names, output from the computer, or code examples. Because of that convention, when I see "try" in courier font,I assume this is a "try" command in Java language. At the same time, in English, the original meaning of "try" is to "attempt".

English speakers should be able to assume those two meanings are included in the courier fonts of try and catch. However, this is a headache for the translator.

By the style guide, translators are instructed NOT to translate courier fonts since they are commands. However, the general meaning of the word, try and catch in this case, has to be translated. ... how could it be ?

Well, one translator did translate "try" and "catch" in Japanese. Then, the command names of try and catch are now missing. Another translator left those in English. Then, the general meaning of try and catch may not be understood.

There is no perfect answer. As a mitigation plan, I put English in courier fonts in brackets and also translated the general meaning such as...


名前からわかるとおり、これらの式は、一部のコードを実行しようと
<literal>トライ (try)</literal> しますが、問題がある場合には例外を
<literal>キャッチ (catch)</literal> します。

This effort will be repeated for the number of languages. However, if the original sentence is written in the following way to avoid "dual meaning" by the font usage, the problem will disappear.


As their names imply, these expressions try to execute some code
using <literal>try</literal> command, but catch an exception by
<literal>catch</literal> command if there is a problem.

In addition, if the writer uses <command></command> tags instead of
<literal></literal> tags, this will improve Machine Translation
quality dramatically. <literal></literal> is only to define the font,
but <command></command> to define the nature of that term as well
as the font. Machine translation engine identifies the tags and
keep that term in English. That's another suggestion for the writing
from localization point of view...

月曜日 2 23, 2009

楽しかった OSC (I enjoyed OSC!)

わーい! 楽しくて苦しい 3 日間がおわりました。一日目は中国から日本に出張にきてくれたボスとのミーティングとチームでディナー (苦しいのはこっちではなくて通勤です!往復 4 時間!)、二日目は OSC 1 日目、そして二日目はいよいよ本番 OSC 2 日目でコミュニティーデー + スピーチする日... ああ、これが緊張するのよ!

OSC 1 日目は静かなスタートでした。でも自分にとっては出展を最初から最後までホストするのは初めてのことだったので緊張しました。これまでは、ほかの人が設定した枠の中でちょこっとスピーチするだけだったので、あらためて、チームメンバーがこれまでしてくれていたことに感謝しました。。。PC をネットに接続したり、デモに使うツールやリンクを設定してくれたり、荷物の配送をしてくれたり、片貝さんには本当にお世話になりました。ありがとうございます!

展示コーナーでは OmegaT プロジェクトの Jean Christophe Helary (JC) さんと一緒に「翻訳・L10n よろず相談」をしました。JC が、キュートな看板を作ってくれたんですよ。写真ができたらアップしますね。

OmegaT に関する質問は JC が、Sun の関わっているオープンソースプロジェクトについてはわたしが答えました。そして、全般に関わること、たとえば「品質を維持しながら、翻訳してくれる貢献者を増やすにはどうすればいいか」といった「普遍的な」問題については、みんなで話し合いました。

1 日目にあった OmegaT セッションでは、JC が 2.0 の機能について話してくれました。わたしがもっとも注目したのは、メモリーと用語集を読み込む早さが超スピードアップしていたこと。これがわたしの悩みの種だったんですよ。解決されたのは、うれしいなあ。

2 日目はコミュニティーデーで、朝からたくさんの方がわたしたちの展示室に来てくれました。OpenOffice.org のメンバーに会えたのも、嬉しかったです。これまでメールでしかやりとりしていなかった人に会えるのは、本当に嬉しい。

さて、(自分にとっては) メインイベントの翻訳セッションが 1 時から始まります。始める前に、PC からプロジェクターにスライドを映してっっと... と片貝さんが設定してくれているのですが、なかなか映りません。10 分前... まだ映りません。6 分前... なんでー? これでいけるはずなのに... 3 分前... 「ホワイトボードに書いて頑張るか」と決意を固めました。

結局、PC (Vista!) はあきらめて、OpenSolaris 経由で (USB で運んで) 映すことに成功しました!よかったーーー。詳しいことはわからないけど、恐るべし Vista。アイラブ OpenSolaris。

あんまり緊張感高まったので、「ネイティブランゲージで話してもいいですか?」と、来てくれた方々にお願いして「大阪弁」でしゃべらせてもらいました。いやー、初めてだったけど、いいね!大阪弁スピーチ。なんにも考えないでも言葉が出てくるって素晴らしい。

OpenOffice.org メンバーの久保田貴也さんが送ってださった写真を、英語のあとにアップしていますので、ご覧になってくださいね。久保田さん、ありがとー。プレゼンの内容については、また後日詳しく書きますね。

English:

Yea-! I've survived my happy&hard three days! Day 1 - Meeting my boss visiting Japan from China and fun dinner with our team (this is not hard, but commute to the office was! -- 4 hours for round trip), Day 2 - OSC 1st day, Day 3 - OSC Community day and ran a talk session.

OSC 1st day was a little quiet, which was good for me to start. This is the first time I experienced whole process of hosting a corner and making a talk session. I used to join just a part of it as a guest speaker, but this time, I was the owner (I realized how many tasks that my colleagues had done for me). I am sure I could not start a day without Masaki's help to make a internet connection, setup all the links and tools on PC, and manage the baggage delivery.

We hosted a joint corner with OmegaT project core contributor, Jean Christophe Helary (JC), with the name "All Sorts of Consultation for Translation/Localization". He created a wonderful sign board for us. (I will show you later when I gets the photo).

He answered questions about OmegaT, and I did about Sun-associated open source projects, and we all discussed together how to lead the translation project - what is the best process to keep quality while increasing the contributors. I know it is a common and good issue to work on for all the projects.

I enjoyed OmegaT talk session by JC. He talked about the new features on 2.0 release. It was great the load time of glossary and memory is improved dramatically! To be honest, that was the major problem for me that loading large reference TM takes so long time.

OSC 2nd day was Community day. It was a big change from yesterday. From the beginning, there were lots of visitors coming to our room. I met two of OpenOffice.org contributors, for the first time, to whom I have been communicating only by email. It was great to see them in person.

My talk session was from 1pm. There was a happening before my talk. My slide could not be projected on the screen with all the connections set up! Masaki and my colleagues worked very hard on the setting, but screen was black... now, it's 10 minutes before the start... still blank screen... 6 minutes, nothing changed... I kept praying... 3 minutes... almost giving up and started to think how I write my thoughts on the white board.

Then, finally, we gave up Windows (Vista!) and transfered my PDF (by USB) to OpenSolaris. Then it worked!
I love OpenSolaris !

I was so nervous and tensed by this happening, so I asked for permission to my audience "May I speak in my native language ?" It is Osaka dialect (Oosaka-ben). They smiled and nodded - thank you!.

Here's some photos an OpenOffice.org contributor, Takaya Kubota, sent me (thanks!).
I will write more about the contents of my preso later this week :-)

月曜日 2 16, 2009

OSC Tokyo/Spring に出展します (Talk&Exibit corner on OSC Tokyo/Spring)

Open Source Conference 2009 Tokyo/Spring というイベントに、「各種翻訳プロジェクト」というアバウトな名前で参加します。(代表名として OpenSolaris 翻訳プロジェクトにしています)

お近くの方は、是非お越しくださいませ。セッションのほかに、展示コーナーも設けています。Mozilla, OpenOffice.org などの近くにいると思いますので、見かけたら声をかけてくださいね。

セッションでは、OpenSolaris、OpenOffice.org、GlassFish、NetBeans での翻訳プロジェクトの活動内容を紹介して、翻訳の面白さ、翻訳という貢献がいかに求められているか、といったことを話したいと思っています。展示コーナーでは、OmegaT プロジェクトと合同で、「翻訳・l10n よろず相談」を行います。翻訳でこんなことで困っているんだけど、、、といったことについて情報交換できるといいなと思います。相談じゃなくても、オープンでフリーで使える翻訳サポートソフトウェアを (知っている範囲で) 紹介したいと思います。今考えているのは、OmegaT、CTI、SunGloss、日本語スタイルガイドです。

http://www.ospn.jp/osc2009-spring/

2009年2月20日(金)・21(土) 10:00-17:30(最終日は16:30まで)

日本電子専門学校 7号館(東京都新宿区・JR大久保駅 南口 徒歩2分

http://www.ospn.jp/osc2009-spring/modules/eventrsv/index.php?id=2&noform=1

13:00-13:45

オープンソースソフトウェアを日本語で使おう !

サンの参加するコミュニティーから翻訳・ローカライズの具体例を紹介

担当:OpenSolaris、OpenOffice.org、GlassFish、NetBeans翻訳プロジェクト

講師:斎藤玲子、片貝正紀(サン・マイクロシステムズ株式会社)

今回は、サンの会社枠ではなく、コミュニティーの一員として出展するのです。片貝さんが一緒に出てくれるんですが、ドキドキします。。。当然だけど、全部自分で準備しないといけないし。。。がんばりまーす。

English:
I am going to make a presentation and host a exhibition corner at
Open Source Conference 2009 Tokyo/Spring, with the very "flexible" name "Various Translation Projects" :-) (though, use the representative name as "OpenSolaris translation project).

Please visit our session and corner if you can! I will be located in the same room as OpenOffice.org or other desktop projects.

In my talk session, I plan to introduce what we are doing with OpenSolaris, OpenOffice.org, GlassFis, NetBeans translation projects, and share how you can enjoy translation and contribution in those projects. Also, I would like to insist how important and welcomed your translation contribution will be. In the exhibition corner, I will offer "Consultation about Translation and Localization" jointly with OmegaT project. What I can do may be limited to what I know, but want to talk to those who are interested in translation/localization. What I and JC (Jean-Christophe Helary) are going to show is OmegaT, CTI, SunGloss, and Japanese styleguide (Open Translation site).

Here is the detail:

http://www.ospn.jp/osc2009-spring/

http://www.ospn.jp/osc2009-spring/modules/eventrsv/index.php?id=2&noform=1

13:00-13:45

Let's use Opensource Software in your language!

We will show examples of Sun-related translation projects.

Project Name:OpenSolaris、OpenOffice.org、GlassFish、NetBeans Translation project

Speaker:Reiko Saito, Masaki Katakai

This time, I will join this event as one of community members, not as Sun. Masaki supports me, but I am very nervous since this is the first time to manage everything myself. But I will pull myself together and do my best!

About

user13133135

Search

Archives
« 4月 2014
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
今日
Bookmarks