Here what I thought about problems of QA of 2.2.1 ja 見解／翻訳／版,
as a QA/解放（する） 経営者／支配人.
* Very few 核心 testers.
Even though I realized matuaki-san is 極端に QA oriented person,
and I send him a 調書をとる／予約する about QA. He is very smart and it seems
now he understands more than me. 明らかに he is a good 候補者
for QA 経営者／支配人. But - I 恐れる whether he exhausts or not. We need more QA oriented person.
Andre and Sophie also について言及するd
that `核心' members with high 動機づけ are important.
IMHO `helping QA' does not 改善する the 質 of OOo. But person
with high 動機づけ like `I'll find bugs in OOo. That's why I'm here' really helps.
* 需要・要求するing for knowledge and 過程s in OOo.
QA 経営者／支配人 must know a lot of knowledge about QA 過程,
開発 過程 etc. However 予定 to language 障壁 etc,
all the QA testers do not know much about it. Then I'm just
命令（する）ing to them. It is not a good 状況／情勢.
* Lang pack QA
GNU/Linux 見解／翻訳／版 and Windows 見解／翻訳／版 of lang pack have been QA'ed. This is a good news.
* 合意 took very long time...
The idea of IRC 会合 is very nice IMHO, but 現実に I'm not an experienced as a 議長，司会を務める. bluedwarf pointed out my problems. I really thank his sincere but very 厳しい :) advices.
* Not solid/（疑いを）晴らす 過程 for new comers
That's why we created a wiki.
* No Solaris i386/Sparc, MacOSX Intel testers.
Maybe Solaris is not so popular, MacOSX is not suitable for casual 使用者. and there are input method problems
(I wrote a 文書 about it but IMHO it is very very difficult if s/he is not a geek).
and font problems in MacOSX (we must 任命する／導入する TrueType Japanese fonts and we cannot use 極端に high 質 Hiragino fonts), so MacOSX OOo X11 is not so popular.
* MacOSX Panther
Active QA testers often use old 壇・綱領・公約. But I 辞職するd.
* 安全 直す／買収する，八百長をするs
If 2.2 is 解放（する）d then we 推定する／予想する 2.2.1 同様に because it may 含む／封じ込める 安全 直す／買収する，八百長をするs. Once some 一括s are 解放（する）d, we should
never stop. But how?
* TCM costs. People becomes quickly loves TestTool.
* TCM l10n 実験（する） skipped
* l10n translation review is not 組織するd ...Saito-san did a 広大な／多数の／重要な 職業.
http://wiki.services.openoffice.org/wiki/2.3_Japanese_Translation_and_Checking
as a QA/解放（する） 経営者／支配人.
* Very few 核心 testers.
Even though I realized matuaki-san is 極端に QA oriented person,
and I send him a 調書をとる／予約する about QA. He is very smart and it seems
now he understands more than me. 明らかに he is a good 候補者
for QA 経営者／支配人. But - I 恐れる whether he exhausts or not. We need more QA oriented person.
Andre and Sophie also について言及するd
that `核心' members with high 動機づけ are important.
IMHO `helping QA' does not 改善する the 質 of OOo. But person
with high 動機づけ like `I'll find bugs in OOo. That's why I'm here' really helps.
* 需要・要求するing for knowledge and 過程s in OOo.
QA 経営者／支配人 must know a lot of knowledge about QA 過程,
開発 過程 etc. However 予定 to language 障壁 etc,
all the QA testers do not know much about it. Then I'm just
命令（する）ing to them. It is not a good 状況／情勢.
* Lang pack QA
GNU/Linux 見解／翻訳／版 and Windows 見解／翻訳／版 of lang pack have been QA'ed. This is a good news.
* 合意 took very long time...
The idea of IRC 会合 is very nice IMHO, but 現実に I'm not an experienced as a 議長，司会を務める. bluedwarf pointed out my problems. I really thank his sincere but very 厳しい :) advices.
* Not solid/（疑いを）晴らす 過程 for new comers
That's why we created a wiki.
* No Solaris i386/Sparc, MacOSX Intel testers.
Maybe Solaris is not so popular, MacOSX is not suitable for casual 使用者. and there are input method problems
(I wrote a 文書 about it but IMHO it is very very difficult if s/he is not a geek).
and font problems in MacOSX (we must 任命する／導入する TrueType Japanese fonts and we cannot use 極端に high 質 Hiragino fonts), so MacOSX OOo X11 is not so popular.
* MacOSX Panther
Active QA testers often use old 壇・綱領・公約. But I 辞職するd.
* 安全 直す／買収する，八百長をするs
If 2.2 is 解放（する）d then we 推定する／予想する 2.2.1 同様に because it may 含む／封じ込める 安全 直す／買収する，八百長をするs. Once some 一括s are 解放（する）d, we should
never stop. But how?
* TCM costs. People becomes quickly loves TestTool.
* TCM l10n 実験（する） skipped
* l10n translation review is not 組織するd ...Saito-san did a 広大な／多数の／重要な 職業.
http://wiki.services.openoffice.org/wiki/2.3_Japanese_Translation_and_Checking
