Unify words in Japanese docs: "分析" or "解析"

[KengoTODA]

Like #1571, some of our document uses "分析" to represent "analysis", and other parts use "解析".

Usually, Japanese developers use "静的コード解析" to represent "static code analysis", so I personally prefer "解析" over "分析". Our messages_ja.xml for bug descripters also uses "解析".

However, for historical reason, FindBugs frequently uses "分析" in manual_ja.xml for http://findbugs.sourceforge.net/ja/manual/. Eclipse plugin also uses "分析" in messages_ja.properties.

We need to consider which SpotBugs officially uses, and unify them to reduce users' confusion.

[KengoTODA]

Maybe messages translated by K.Hashimoto like c694c4f use "分析".
He (she?) contributed to the Eclipse plugin and FindBugs website mainly.

And messages translated by @orihalcon128 and others like eb5e797 use "解析".

I prefer to replace "分析" with "解析" because I believe "解析" is a modern translation.
@wreulicke @orihalcon128 Any thoughts? Thanks in advance!

[KengoTODA]

According to Google Trends, "解析" is more popular than "分析".

https://trends.google.co.jp/trends/explore?cat=1227&geo=JP&q=%E9%9D%99%E7%9A%84%E3%82%B3%E3%83%BC%E3%83%89%E8%A7%A3%E6%9E%90,%E9%9D%99%E7%9A%84%E3%82%B3%E3%83%BC%E3%83%89%E5%88%86%E6%9E%90,%E9%9D%99%E7%9A%84%E8%A7%A3%E6%9E%90,%E9%9D%99%E7%9A%84%E5%88%86%E6%9E%90

[orihalcon128]

I prefer "解析" as well.

Why "分析"?
https://ja.osdn.net/projects/mergedoc/forums/2758/38853/

[KengoTODA]

Pleiades 全体では analysis は "分析" としているため、調整する可能性があります。

Ahhhh.... I see. Thanks orihalcon128 for your information sharing!

[KengoTODA]

So for Eclipse (Pleiades) users, "分析" is better. However, SpotBugs/FindBugs bug descriptions already use "解析" so this mismatch is already common for them.

Then I hope that we can use "解析" as our official term, and it won't damage the experience of Eclipse (Pleiades) users.