Update "LinuxBuildInstructions" please

[GoogleCodeExporter]

The "LinuxBuildInstructions" is hard for most users.
http://twitter.com/#!/NormaJeanCogito/status/171831632830021632

I think this is more easy.
http://code.google.com/p/mozc/wiki/LinuxBuildInstructions
--------------
Get the Code
Download the latest <a 
href="http://code.google.com/p/mozc/downloads/list">mozc</a>.

Compilation
% cd mozc-VERSION/

If you need the zip code dictionary ("106-6126", 
"東京都港区六本木六本木ヒルズ森タワー"), please get them.
% cd data/dictionary/
% wget http://www.post.japanpost.jp/zipcode/dl/kogaki/zip/ken_all.zip
% wget http://www.post.japanpost.jp/zipcode/dl/jigyosyo/zip/jigyosyo.zip
% unzip ken_all.zip
% unzip jigyosyo.zip
% python ../../dictionary/gen_zip_code_seed.py >> dictionary00.txt
% cd -

(Ubuntu, Debian)
% svn checkout http://mozc.googlecode.com/svn/trunk/src/debian
% debuild -b -uc -us
--------------

Original issue reported on code.google.com by heathros...@gmail.com on 22 Feb 2012 at 12:26

[GoogleCodeExporter]

Original comment by yukawa@google.com on 1 Apr 2012 at 2:20

• Added labels: OpSys-Linux

[GoogleCodeExporter]

Short answer is our site is intended for developers rather than end-user.

The primary goal of LinuxBuildInstructions page is sharing how our team is 
building Mozc on Linux platform. (And this is why we don't put the build 
instruction from tar ball at the top of the page; we are always downloading 
source code from the repository and building Mozc with build_mozc.py command in 
daily development).

In his case, the best way is using official binary package on his (Linux?) 
platform IMO. It should be far easier and safer for most of users than building 
Mozc from source code, isn't it?

Regarding Japanese postal code, I added some descriptions in AboutMozc.
Thanks,

Original comment by yukawa@google.com on 2 Sep 2012 at 1:10

• Changed state: Done