Home

FutureGadget

メモ – テストデータ生成サービス「generatedata.com」

テストデータ生成サービス「generatedata.com」

■概要

JavaScript, PHP and MySQLベースの「generatedata」のオンライン版。
GNU GPL v3ライセンスでソースコードのダウンロードが可能。

http://www.generatedata.com/

■主なフィールド型

  • 人・プロフィール属性関連
  • 住所・国・地域関連
  • 貨幣・クレカ関連
  • 文字列・数値
  • その他(コンストレイント系)

■出力形式

  • CSV
  • Excel(.xls)
  • HTMLテーブル
  • JSON
  • LDIF
  • SQL
  • XML
  • コードでの変数定義(Javascript、PHP、Perl、Ruby)

■制限

オンライン版は登録無し(未寄付)だと下記制限あり。

  • 生成行は100行まで(登録すると5000行まで)
  • 日本語辞書無し(未確認:以前は存在?)

■要確認事項

  • PHPビルトインサーバで動作可能か?
  • DL版の辞書を日本語に置き換える手間
  • 生成設定のプリセット保存の可否
  • DBMonsterとの比較

Lubuntu、オレオレ初期設定

入れるパッケージ、その他設定

→続きを読む

Blender日本語翻訳 作業項目

Blender日本語翻訳作業全体図

XLIFFDiffの使い方

BF-Translation-dev管理者っぽい人の言うBCon

*翻訳者は/trunkを変更しない。/branchesのみ変更する。
*翻訳者は新言語を追加するときは管理者に確認しなければならない。

BCon1: 10月20日 (define targets, get branches reviewed & ready)
BCon2: 10月30日 (add branches to svn)
新言語ファイルの追加可能。
/branches以下のpoファイルの更新は1週間ごとに行われる。(金曜朝が良いと思われる)
そして大規模なソース変更(ブランチマージのような)が発生する可能性がある。
/trunkもまた一週間ごとに更新される(月曜夕方)。
そのたびにに翻訳度は0%になる(trunkにある全ての言語が)
これはコントロールします。

BCon3: 11月15日 (testing fixing period)
BCon1とBCon2と同様だが、新言語ファイルの追加は不可。

BCon4 (i.e. RC): 12月1日 (testbuilds, fixing only)
RCの初リリース前に、翻訳度80%の言語ファイルのみが/trunkの最後の更新をされる。
(つまり、/trunk内の完成間近の言語のみ対象)
そして/trunkは致命的な問題でもない限り、それ以上は変更されない。
/branchesは解放状態のまま、1週間ごとに更新される。

BCon5 (i.e. freeze and release): 12月11日 (svn frozen, release a few days after)
/trunkは凍結されたまま(致命的なバグフィックスだけ行われる)。
/branchesは解放状態のまま、1週間ごとに更新される。

 

* Translators should never modify themselves /trunk. They should only
edit /branches.
* Translators should ask an admin to add a new language (as this also
implies, currently, some code in Blender).

BCon1: 20 October (define targets, get branches reviewed & ready)
BCon2: 30 October (add branches to svn)
New languages can be added.
An update of all po’s under /branches is made at least once a week
(friday morning seems a good option, imho), and possibly more often
in case of big changes in sources (like a branch merged). I can
handle this.
The /trunk is also updated once a week (monday evening, imho). The
threshold
is set to 0% (i.e. all existing languages are in trunk). I can
also handle this.
BCon3: 15 November (testing fixing period)
Like BCon1 and 2, but adding new languages is no more allowed.
BCon4 (i.e. RC): 01 December (testbuilds, fixing only)
A last update of /trunk is done just before first RC, using a
threshold of 80% (i.e. only
nearly finished translations are in /trunk). Then, /trunk is no
more changed,
unless a serious issue arises (can’t imagine what, but you
never know…).
/branches remains open and updated once a week.
BCon5 (i.e. freeze and release): 11 December (svn frozen, release a few days after)
/trunk is also freezed (only critical bugs are fixed! :P ).
/branches remains open and updated once a week.

 

※訳注
・誤訳してたらすんまそん
・BConスケジュールは下記から抜粋
http://wiki.blender.org/index.php/Dev:Doc/Projects

BL-i18Nの作業体制構築で必要と思われる作業・情報

■BF-Translation-dev管理者っぽい人の発言要約
■↑翻訳率45%の根拠調査
■GSoC時代のマージ方法(できればXliffDiff再配布したい)
■翻訳作業全体図の明確化
■BFの開発スケジュール(BCon)に準じたある程度のスケジュール立案
■翻訳サイクルの明確化
■新マージ方法を共有
■日本語化まとめサイト更新
■スプレッドシート更新方法の共有
■各種情報のURLメモ
■各種ファイルの説明
■gettextの仕組みの説明

BF-Translation-dev管理者っぽい人の発言まとめ

Evening Amin,

Please avoid mailing such big mails, I had to authorize it by hand! ;)

I’ve added the fa branch to the bf-translations svn, with your po and conversion script (seems the best place for it, imho).

Now, please register an account on projects.blender.org (if you do not have one yet), and request membership to http://projects.blender.org/projects/bf-translations/ . This will give you access to the svn repo, where you will be able to commit updates of your work (in branches/ part, please).

Best regards,
Bastien

You could for example use rapidsvn, an easy multi-OS GUI over svn: http://www.rapidsvn.org/index.php/Documentation

The svn repository you need to checkout is https://svn.blender.org/svnroot/bf-translations , and your svn login and password should be the same as your projects.blender.org ones (iirc…).

You’ll see, it’s not difficult :)

Hey Dalai,

I already updated all po in branches last friday (svn62, against Blender svn 41002), and I intend to do so each friday. :)

I developped a bunch of py scripts to do it automatically (under /trunk/po currently, but I’m rewriting them in a much consistent whole, should commit in one or two days).

As for the 2.60 release, we wil only have new es, zh_CN and fr translations (all above 80%) ? I updated them in Blender trunk yesterday, and was already yelled at, because this should have been done before RC1 (or at worst, RC2)… So nothing more will be added/updated for 2.60!

Regards,
Bastien

Hi,

I’ve spent the last days working on the i18n stuff both py tools and
leaning i18n usage in Blender code (I’ll talk about that on bf-committers).

I intend to commit this very soon (likely tomorrow thursday), unless
some serious objections arise. :)

Here is a summary of the changes in scripts (see also the whole new
README.txt file for details:
http://wiki.blender.org/index.php/User:Mont29/i18n ):
* Rewrote all scripts:
** They are now under /trunk/po/tools dir.
** They use a common settings.py settings source.
** Commonly used functions are gathered in utils.py (notably those
reading/parsing and writing po messages).
** All scripts now have an args management system (argparse module),
with a minimal help message (-h).
* Nearly all common operations can now be done with two tools:
** update_branches.py to update /branches po’s with latest messages.
** update_trunk.py to update /trunk po’s and mo’s with /branches po’s
translated enough.
* Lower-level scripts remain present, for more specific needs.
* merge_po.py now accepts several sources po’s to merge into dst one
(and it removes fuzzy flag when needed).
* check_po.py is now a report-only tool outputing some nice stats and
info about current po’s.

Another important topic: languages needing post-processing of their po’s
(currently, arabic and persian). I renamed the scripts to
<language>_to_utf.py (and fixed a bug regarding escaped \” and \t in
messages…). So now, the <language>.po file *must* be the raw
(unprocessed) one.
Then, the import_po_from_branches.py script (and hence the
update_trunk.py one) will use that <language>_to_utf.py script, if
present, to automatically process the raw <language>.po file and put the
processed version under /trunk/po.

I hope and think all this will hugely ease to use and manage the
bf-translation repo!

Best regards,
Bastien

Hi,

Here is a proposition about managing bf-translations repo, and how to
synchronize with Blender release cycles.

* Translators should never modify themselves /trunk. They should only
edit /branches.
* Translators should ask an admin to add a new language (as this also
implies, currently, some code in Blender).

BCon1: 20 October (define targets, get branches reviewed & ready)
BCon2: 30 October (add branches to svn)
New languages can be added.
An update of all po’s under /branches is made at least once a week
(friday morning seems a good option, imho), and possibly more often
in case of big changes in sources (like a branch merged). I can
handle this.
The /trunk is also updated once a week (monday evening, imho). The
threshold
is set to 0% (i.e. all existing languages are in trunk). I can
also handle this.
BCon3: 15 November (testing fixing period)
Like BCon1 and 2, but adding new languages is no more allowed.
BCon4 (i.e. RC): 01 December (testbuilds, fixing only)
A last update of /trunk is done just before first RC, using a
threshold of 80% (i.e. only
nearly finished translations are in /trunk). Then, /trunk is no
more changed,
unless a serious issue arises (can’t imagine what, but you
never know…).
/branches remains open and updated once a week.
BCon5 (i.e. freeze and release): 11 December (svn frozen, release a few days after)
/trunk is also freezed (only critical bugs are fixed! :P ).
/branches remains open and updated once a week.

Now, fire your comments and suggestions! When we get a consensus, I’ll
write a wiki page about it (anyway, we lack some doc about all this!).

Best regards,
Bastien

Hi,

bf-translations update is done! I also updated all branches’ po’s against latest big i18n commit in trunk (svn41149).

Please have a look at those commits:
* http://lists.blender.org/pipermail/bf-translations-svn/2011-October/000082.html
* http://lists.blender.org/pipermail/bf-translations-svn/2011-October/000083.html

I also created this page (which currently has the same content as README.txt): *http://wiki.blender.org/index.php/Dev:2.5/Doc/How_to/Translate_Blender*

Best regards,
Bastien

Hi,

We have a new language: Indonesian (id). Welcome on board! :)

I just updated both branches and trunk ? please update your po’s.

Here are current branches’ stats:
Checking /home/i7deb64/blender-2.5-svn/__work__/i18n/branches/ja/ja.po…
Stats:
45.5% done! (4259 translated messages over 9353).
28.5% of messages are tooltips (2670 over 9353).
31.2% of tooltips are translated (833 over 2670).
19.6% of translated messages are tooltips (833 over 4259).
0.2% of messages are commented (23 over 9376).
This translation is currently made of 46757 signs.

blender日本語翻訳作業まとめページ

—-作業者MTGまとめ 07/30————————————————————–

■進め方・初動に関するまとめ
・2.49bのja.poをガーリックのpotファイルにマージし、これをベースとする(shizu)。
・各自の翻訳作業はまずは始めてもらい、タイミングを見てベースにマージする。
・WEB翻訳システムに関してはツイ子さんのpootleを使わせていただく(http://j.mp/oxr0Ak)。
・翻訳作業に関わるやりとりは基本的にtwitterの「#b3d #blender日本語化」ハッシュタグで行い、
IRCは判断しづらい不明点などが出てきたときの意見調整に利用する。

■その他
・マンパワー確保のために翻訳作業お手軽参加ガイドラインが必要。
・Blender-Translation(google code)との調整はshizuが行う。
・翻訳作業の締め切りは設定されていない。
※Blender-Translationでの認識はv2.6のリリースに間に合えばとのこと。

■備考
・「2.49bのja.po」というのは現公式リリースに含まれているja.poのこと。
※2.49bリリースから更新されてないはずなので、これが正式最新であるという認識。
※実際はblenderのtrunkから取得します。
・ガーリックのja.poは新しい翻訳対象文字列追加の過程で支離滅裂になっており、クリーニングが必要。
※ベースを2.49bのja.poとガーリックのpotファイルとマージして作るのはクリーニングのためです。
・pootleを使わずにローカルで編集作業する場合、マージのために
どこを作業したか差分を取れるよう、作業前のファイルも残しておいていただけると助かります。

→続きを読む

Blender日本語化関連メモ

http://projects.blender.org/projects/bf-translations/

https://sites.google.com/site/blugjp/blender-translators

http://ux.getuploader.com/blender_translation_jp/

https://svn.blender.org/svnroot/bf-blender/trunk/blender/po/

http://code.google.com/p/blender-translation/

http://groups.google.com/group/blender-translation

http://blender.jp/modules/news/article.php?storyid=3419

http://wiki.blender.org/index.php/User:Xiaoxiangquan

/GoogleSummerOfCode/2011/Internationalization#Notes_for_Translators

https://launchpad.net/~bf-translators

https://wiki.ubuntulinux.jp/Develop/TranslationGuide

http://blenderartists.org/forum/showthread.php?224545-Multiple-Language-Translators-Wanted-for-GSoC-Garlic-Branch

http://tuiko.dip.jp/

Home

Search
Feeds
Meta

Return to page top