木曜日 12 23, 2010

JTF Translation Festival 2010 - MT&Post Editing

さきほどのエントリに続き、次は MT とポストエディットについて。今回は日本語で話します。(I will write in English after the Japanese section).


機械翻訳 (Machine Translation, MT) が導入されて、ずいぶん改良が進んできました。一般的な表現なら、無料翻訳エンジンを使えば、だいたいの内容が正しく出力されます。では、翻訳業界ではどうでしょうか。翻訳会社で MT を導入してソリューションを提供する場合と、発注する会社が MT を導入してコスト削減・ボリューム増量を図る場合が考えられます。


しかし、いずれの場合も、MT の結果をそのまま使用するのはごく一部です。まだ、事後処理、つまりポストエディットが必要です。このポストエディットが翻訳者を悩ませます。どこまで直せばいいのか?こんなことなら自分で翻訳した方が早い... おしまいには、何のためにポストエディットしているのかわからなくなります。ポストエディットの効率を計測するテストでは、不満を持ちながらポストエディットした人の方が、そうでない人より効率が下がることがわかっています。


どうして不満を持ってしまうのか?それは、「こうであるべき」という目標設定を達成できないからです。もっといい方法 (支援ツールを使いながら自分で訳す) がわかっているのに、違う方法 (MT のポストエディット) をしないといけないからです。でも、その「こうあるべき」は、正しい前提でしょうか?


MT は、これまでの翻訳市場に割り込むものではなく、市場を広げるものだと考えてたらどうでしょう。今までは翻訳されていなかったものを、翻訳するためのツールであると。そうすると、MT のポストエディットは、これまでとは違う目標設定とマインドセットで行う必要があります。それは、何か?


上記のようなテーマで、お話した内容がこちらのスライドです。Q&A では、たくさんの質問をいただいて、楽しかったです。また機会があれば、みなさんともっとお話したいと思っています。


English:


It has been a while since Machine Translation (MT) appeared in the world, and it's been improved in the quality quite a lot.  We can see the common expression is translated correctly with most of the free translation engines.  Now, how about in the translation industry ?  More and more companies started to consider MT as a realistic solution to provide information more quickly and more reasonably to the customers, and some translation companies started to use MT as one of the solutions to those companies.


However, still it is only a part of the translation to use MT output without editing.  MT needs Post Editing.  This is a head ache of translators.  How far should I correct MT output ?  I could have translated more correctly.  Why should I edit this !?  In the end, I do not understand why I should edit MT output.  I cannot find a reason.  ... that's was my case at the beginning.  It is true unhappy translators are less productive in post editing, which was confirmed in one of the post editing productivity test. 


Why are they unhappy ?  It is because they cannot meet the goal that they have in their mind.  They know the better way, but they have to stick to the MT+Post Editing.  Now, let's think about the goal.  Is it appropriate to this case ?


How about thinking this way - MT is not the invader or intruder to the existing translation market, but it is the one to create a new market ?  How about taking MT as a tool to translate the new contents which we cannot translate because of the volume and cost restriction ?  Then, we should create a new goal and mindset to work with MT.  What are they ?


I talked about such kind of details in my session, and here is the slide.  I wanted to make it interactive session with many Q&As, and I am happy about the results.  But I wanted to have more time... maybe next time.  Talk to you all again :-)







水曜日 8 04, 2010

Talking about "Open" at TC Simposium (JTCA)

こんにちは!しばらく更新していませんでしたが、近況報告します。

オフィスがオラクル青山センターに移りました。新しい場所、新しいマシン、新しいネットワーク... 新しいことづくめで頭がクラクラしていますが、引越しして約 1 ヶ月半で、なんとか落ち着いてきました。何より戸惑ったのは、ウィンドウシステムです。コマンドライン使いたいっ!!!とあせる気持ちをなだめつつ、同じことをするにはどうすればいいのか、と試行錯誤を繰り返してきました。vi が使いたい、grep したい、スクリプトでバッチ処理したい、... プラットフォームが変わっても、探してみると便利なツールがあって、やろうと思えばできるものです。何より、「これ、どうすればいいの?」と悩んだときに、ネットで探すとどこかに回答があるのが嬉しい。まだまだ修行中ですが、以前のスピードを取り戻し、追い越すぞと頑張っています。新しい同僚のみなさんが優しく忍耐強く教えてくれるので、本当に心強いです。

さて、最近やっていることを一部紹介すると... OpenOffice.org 3.3 の翻訳 (わたしは査読担当)、TC シンポジウム 2010 のパネルディスカッションの準備などです。


  1. OpenOffice.org 3.3 翻訳プロジェクト

  2. TC シンポジウム 2010 (私のパネルは 8 月 24 日、2 時より新宿にて)

OpenOffice.org 3.3 は、UI が終わってヘルプの翻訳中。今回のリリースから、翻訳プロジェクトのコーディネーターが大槻さんに変わり、さらにパワーアップしているなと感じます。メーリングリスト で査読コメントや質問への回答を募集しています。ヘルプ締め切りまであと 1 週間強。頑張っていきましょう。

TC シンポジウムでは、「オープンの概念が翻訳を進化させる。~翻訳の仕方はひとつじゃない。翻訳の新たな選択肢」というタイトルで、パネルディスカッションをします: http://www.jtca.org/symposium/2010/panel_tokyo.html#02

オープンソースって何?翻訳する人にとって、どういう関係があるの?何のメリットがあるの?... という質問に答えます。「オープンソースで翻訳する人が増えている」「翻訳支援、機械翻訳などの技術が進歩している」という中で、プロの翻訳者には何が求められているのか?それを会得するには、どうすればいいのか?... そんなこともディスカッションの中で考えていきたいと思っています。みなさん、見に来てくださいね!

English:

Hi!! Long time no update. Now, let me share how I have been doing lately.

I moved to a new office (for me), Oracle Aoyama Center (aka. OAC). New place, new office layout, new machines, new network... everything is new and I has been overwhelmed for a month and a half. The most surprising is office cube. The cube is not actually a cube. It's a combination of small desks and no partition. I can talk to anyone without standing up! I can see who is sitting and who is out. It's a cultural shock ;-) ... but I am sure I will enjoy it.

Well, that is not "most" surprising. It is a window system. I have been working on UNIX for years, and I admit I am an application user, rather than command line developer, but ... still I was shocked to realize I have to do everything by mouse ! I have to fight against my desire "I want to type on command line!", and have been trying to find out how to do the same thing in the current environment. I want to use vi, run grep, write shell scripts... after many try & errors (many many errors), I came to know ... there is a way! Actually, there are many many convenient and useful ways! It is also great I can search on the internet to find many others comments and hints. Still I am struggling but I am sure there are hundreds of ways to do the same or even better things in a different environment. It's always me and how I think that determines what I can do. My new colleagues are all very supportive, patient with my stupid questions, and friendly. I really thank them.

Now, let me introduce some of what I have been working on lately: OpenOffice.org 3.3 translation/review, and TC Symposium 2010 (Panel Discussion about Open Source and Translators).


  1. OpenOffice.org 3.3 Translation Project

  2. TC Symposium 2010 (My panel discussion is on August 24th, 2pm at Shinjuku)

OpenOffice.org 3.3 finished UI translation and now is translating Help. We have a new translation project coordinator, Takeshi Otsuki, and the project is more and more powerful and energetic. We are discussing issues and questions by Translation mailing list. We have 1 week+ until Translation freeze date, and your feedback/comments are always welcome.

In the TC symposium, I will join the panel discussion titled "Openness makes Translation evolving! - Do you have alternative way to do your translation job ? Suggestion for another and free choice.": http://www.jtca.org/symposium/2010/panel_tokyo.html#02

We will answer the questions such as "what is Open and Open Source?", "What matters to translators ?", "What is the advantage for me?"... We also discuss what is the "core competency" for translators and what to do to acquire that skill it in the current changing situation - more and more people translate in Open Source projects, and more and more technologies are introduced such as Machine Translation. Please come and see us on August 24th from 2pm at Shinjuku!

水曜日 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 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 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 :-)

月曜日 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...

水曜日 12 10, 2008

Sun Tech Days の思い出 (Memories of Sun Tech Days 2008)

すでにタイトルは「思い出」となっていて、まるで去年のことのようですが。。。今日は Sun Tech Days 2008 の感想を書いてみようと思います。

昨年は「オープンソースソフトウェアを日本語で使ってみませんか?」というメッセージでした。一歩進んで今年は「日本語コミュニティーに入ろう」という部活の勧誘の装い。各コミュニティーで何をやっているか、どうやったら入れるか、どんなことができるのか、わかるのか... などをまとめた冊子を配り、各種プロジェクトの担当者がブースに立って説明・お話して、率直な感想やご意見を伺う... ということをやりました。

わたしの感想は... 日本語コミュニティーのことを知っている人が増えて嬉しい! というのが一番。二番目は、メールでしか話したことのない方々と直接会えて話すことができて楽しかった! です。一日目のレセプションでは飲んだり食べたり、ちょっとしたパーティー気分でリラックスしてお話できたし。

記念すべき、わたしの「初めて」は、Lightening Talk に参加したことでした。ほかの人みたいに上手に面白くはできなかったけど、でも頑張ったからいいもん! と自分を励ます私。話した内容は OpenSolaris 日本語プロジェクトでした。ここにアップロードしておきますので、よろしかったらご覧になってください。

そして、記念撮影をぱちり。
同僚の俣野宏子さんと

English:


The title is like a memory of long time ago... but it's just a week! I am going to write about what I felt at Sun Tech Days 2008.

Last year, our message was "Why don't you use Open Source Software in your language ?". This year, "Let's join Japanese community of your favorite OSS software" - a big step forward. I realized more and more people recognize what's community and are interested how to join. This year's Pod activity is like a college festival - inviting new graduates to our "club" activities. We handed out Sun Community Guide Book, introduced the projects by responsible engineers, talk and exchange thoughts with users...

My overall comments are ... No.1: I was very happy to see more people are aware of or interested in OSS and it's Japanese community. No.2: I was excited to meet people in person, especially those who I talked with only by emails. We enjoyed drinking and eating at the reception on the first day evening together.

My momentum is the first experience of making Lightening Talk. I wished I could have made a enjoyable presentation with lots of humor like others, but I did my best... (so, it's OK OK, Reiko! -- I am talking to myself ;-) ). What I talked about is OpenSolaris translation project. Here's the slide that I translated for this blog :-)

Here's a snap from our Pod...With my fried and colleague, Hiroko

月曜日 12 08, 2008

誰か 2008.11 Release Notes 翻訳してください (Anybody translate 2008.11 Release Notes ?)

まだ manpage プロジェクト進行中ですが、ここで緊急のお願いが! どなたか、2008.11 Release Notes を翻訳してくれる方、いらっしゃいませんかーーー? 諸事情により、リリースノートについては社内で日本語版を翻訳できるかどうか微妙なところなのです。内容はバグのリストで、分量は 6000 words (A4 x 25 pages ぐらい)、フォーマットは HTML です。日程は...

- 12/8-9: 募集期間 (この間に、どなたか「やってみようか」と声を掛けてください)

- 12/8-15: 翻訳期間 (12/15 中にファイルを reiko-dot-saito-at-sun-dot-com 宛てに送ってください)

- 12/16: わたし (斎藤 玲子) が査読させていただきます。必ずフィードバック差し上げます。

- 12/17: 仕上げ・Web に載せる

... と、鬼のようなハードスケジュール。。。「なんじゃそりゃー!」という声が、ちゃぶ台と一緒に飛んできそうで怖いです。... しかしそこを何とか... どなたか協力していただけませんか ? :-)

詳細は、wiki ページにあります: http://wikis.sun.com/display/g11n/Japanese

OmegaT などの翻訳メモリーは使っても使わなくても、どちらでもいいです。とにかく、日本語にするのに協力してください。よろしくお願いします!


English:

Though the manpage translation project is still on its way, now I have an urgent request for all who is interested in OpenSolaris and/or translation. We need help for 2008.11 Release Notes translation for Japanese ! For some reasons, Sun may not be able to translate 2008.11 Release Notes on time. It would be great if somebody helps us to translate this document. Release Notes is like a list of bugs and their workarounds. Format is HTML, and volume is approximately 6000 words (can be converted into 25 sheets of Letter-size paper). The schedule is ...

- 12/8-9: Waiting for contributors (If interested, please let me know)

- 12/8-15: Translation (Please send me translated file by 12/15 at reiko-dot-saito-at-sun-dot-com)

- 12/16: I will review your translation and send you feedback.

- 12/17: Finalize and publish to Web.

... I know it is extremely tight schedule. (I see you are about to throw the things to me...) but, don't be mad and help us please? :-)

Details are up on the wiki page: http://wikis.sun.com/display/g11n/Japanese

This time, using Translation Memory Editor like OmegaT is not mandatory. Just help us to translate 2008.11 Release Notes into Japanese. Looking forward to hearing from you!

金曜日 11 28, 2008

準備完了 !? Sun Tech Days 2008 - Globalization Pot

ああ、やっとブログに書ける状態になりました。Sun Tech Days のグローバリゼーションブース (展示) で紹介する内容が形になってきた〜。よかった〜。今回のテーマは「日本語コミュニティーを知ってますか?」です。知っている人は、入ってください。入っている人は、何か一緒にやりましょう!というメッセージです。パネルは、共通のもののほかに、こんなのを作りました。

ブースではサンと関わりのある日本語コミュニティーのことを紹介する小冊子を配付します。手作りなので、ふつーのコピーにホチキス止めですが... 愛と熱意はいっぱいこもっていますよ!このほか、進化した翻訳ツールの紹介や、コミュニティーキャラクター診断ソフト (お遊びソフトです) も。。。12/2, 3, 4 の 3 日間、会場でお待ちしています。

English:

Finally! I can write this on my blog. The messages and contents of what we will exhibit at our Globalization Pod is almost finalized. Huuuu.... I could not sleep well until today, counting the remaining days. The message for this year is "Do you know Japanese communities ?". If you already know, "Let's join one of them", if you already in a community, "Let's do something innovative together!". We are going to use the standard panel and customized one like this (2nd page is in English).

We will hand out the booklet illustrating various communities related to Sun. It is 100% hand-made and very simple ... plain paper with staples... but! I am proud that we put all of our Love and Passion in it!! Other than this, we will show you advanced translation tools and character analysis software (game). I am looking forward to seeing you on Dec 2, 3, and 4 at Tokyo Midtown.

月曜日 11 10, 2008

もうすぐ Sun Tech Days! (Sun Tech Days coming soon!)

気が付けば、前のブログから 1 ヶ月もたってしまっているではないですか ! いけないわ〜。思っているだけじゃなくて、言葉にしていかないと。

このごろ寒い日が続きますね。鼻がツンとして、ほっぺたが冷たくて、「えっ、12 月だっけ !?」と気持ちがあせってしまいます。12 月には Sun Tech Days があるんですよ〜。

今年も出します、コミュニティーの展示コーナー。去年の展示では「オープンソースソフトウェアを翻訳しよう」というメッセージを出して、翻訳に関するツールの紹介をしました。あれから 1 年、より多くの OSS で日本語コミュニティーが生まれ、育ってきています。今回は、それらの日本語コミュニティーを紹介して、一緒に何かしようよ、というお誘いの場にしたいと思っています。

今、ちょうどパネルを作成中... このほかに、各コミュニティーを紹介する小冊子、あなたはどんな OSS ユーザー? という診断をするゲームなど、企画中です。うふふ、自分が一番楽しみだったりして。

English:

Wow! It's been a month since I wrote my last entry. How bad girl I am. I know I have to express what I am thinking more often. I've been thinking only in my head and did not express enough to all.

It's been cold these days. Chilly wind clears my sinus and freezes my cheek... it is an exceptional weather at this time of the year, and I feel as if it is already happy Christmas season. Talking about Christmas, we will have another happy festival in December: Sun Tech Days 2008!

We're going to host Community Pod again. Last year, our message was "Let's translate Open Source Software in your language", and we introduced various translation support tools. It's been a year and more and more Japanese communities were born and raised for various OSS. This year, we will introduce them one by one and invite you to join us.

Now, I am making the panel to tell our message - Join Japanese community. In addition to that, we are planning to present a booklet carrying JA community information, "What type of OSS user are you?" game, and etc... yes, I am already enjoying this event. Planning is so much fun.

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