search

Santhu / mozc

Automatically exported from code.google.com/p/mozc
0 stars 0 forks source link

Make mozc a library #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
There are several reason for this:
1. make others can easily port mozc to other platform.
2. port can use different release cycle with mozc. Since port might meet API 
break upstream, but it's not the time for mozc to release a new version.

Otherwise the only way is join mozc, or fork mozc in another place.

Both of them is not a good idea. Fork might not have upstream updates in time. 
For join the mozc, just check the reason 2.

For the real world bad examples, just check the ibus build issue in the issue 
list.

Original issue reported on code.google.com by wen...@gmail.com on 8 Feb 2012 at 5:27

GoogleCodeExporter commented 9 years ago 
Hi Weng,

Even for the client-side of Mozc, we do not have any plan to make a library.
It is nice to have of course, but not a high priority task for us.
As long as Mozc is released as a code branch from "Google Japanese Input",
this situation is not likely to change because we are developing
"Google Japanese Input" as a product for end users, not a library for third 
parties.

Regards,

Original comment by yukawa@google.com on 19 Feb 2012 at 11:55