Closed GoogleCodeExporter closed 9 years ago
> Issue 145 requires a debug build.
Maybe this is my mistake.
I applied "emacs_fix.patch" and it killed the usage window.
( Issue 146 )
Please close this issue please.
Original comment by heathros...@gmail.com
on 28 Mar 2012 at 7:50
> Will it send extra info to Google?
No.
Regardless of the build configuration (Debug/Optimize/Release), on all the
supported platforms (Chromium OS, Windows, Mac and Linux), Mozc is designed not
to access any external network resource. Furthermore, we
are planning to remove libcurl4-openssl-dev from the build dependencies on
Linux in the next release because we have no plan to enable network-related
features such as Cloud Sync, Cloud Handwriting, or crash reporting on OSS Mozc.
As for build configuration, mozc_renderer should work with Release build as of
r105 but debug build might be appropriate for such experimental feature because
it enables more assertion checks so that any unexpected situation can be
detected. Anyway please beware that Mozc team has not finished all the porting
tasks of mozc_renderer for Linux and it is still experimental feature, which is
not enabled by default.
As for documentation, we might want to have some feature matrix between Google
Japanese Input and Mozc on this site as Chromium project has in their site as
follows.
http://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome
But I don't think it is so urgent task as for now.
Original comment by yukawa@google.com
on 29 Mar 2012 at 1:30
Added AboutMozc page to this web site.
Original comment by yukawa@google.com
on 28 Apr 2012 at 9:42
Original issue reported on code.google.com by
heathros...@gmail.com
on 28 Mar 2012 at 2:59