Search Criteria
Package Details: mozc 2.28.4715.102-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mozc.git (read-only, click to copy) |
---|---|
Package Base: | mozc |
Description: | The Open Source edition of Google Japanese Input |
Upstream URL: | https://github.com/google/mozc |
Licenses: | custom, BSD, LGPL, Apache |
Conflicts: | mozc-ut |
Submitter: | ponsfoot |
Maintainer: | Nocifer |
Last Packager: | Nocifer |
Votes: | 69 |
Popularity: | 2.69 |
First Submitted: | 2010-08-09 04:27 (UTC) |
Last Updated: | 2022-04-30 07:33 (UTC) |
Dependencies (8)
- qt5-base (qt5-base-git, qt5-base-headless)
- bazel (bazel-git, bazel024-bin, bazel024, bazel2, bazel3, bazel3-bin, bazel31, bazel31-bin, bazelisk, bazelisk-bin) (make)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
- python (python38, python36, python37, python3.7, nogil-python, python311, python39) (make)
- emacs-mozc (optional) – Emacs integration
- fcitx-mozc-ut (optional) – Fcitx integration
- fcitx5-mozc-ut (optional) – Fcitx5 integration
- ibus-mozc (ibus-mozc-ut-united) (optional) – IBus integration
Latest Comments
renatoliveira commented on 2022-02-21 20:25 (UTC)
Cool, that really helped with the problem. I also had to delete the cache from pacman though. Then it worked.
Many thanks. :)
Nocifer commented on 2022-02-21 10:28 (UTC)
These errors are because the recently updated GCC 11.2 toolchain has some internal changes that make cached files from previous builds with older GCC versions no longer valid. Just delete your Bazel cache folder and it should work.
renatoliveira commented on 2022-02-21 10:21 (UTC)
Build fails during installation for me with the following error:
I'm guessing some file directive could be edited to add the dependency declarations it is missing, but I'm not really a C or C++ expert, so I don't know what to do in this case: if it is an issue with the PKGBUILD or with the program's build script. If it is the later then I'm guessing it would be better to open an issue on GitHub instead? :)
Nocifer commented on 2021-11-02 10:57 (UTC) (edited on 2021-11-02 12:42 (UTC) by Nocifer)
@ruahcra Indeed; and when we're talking about an "old commit", we're really talking about a 3-year old version which still depends on deprecated stuff like gtk2 and python2 and a deprecated build procedure/system (for better or worse, upstream has switched out Ninja for Bazel since a few months ago).
Also, yeah, Mozc only releases new versions by commit (internally they're tagged as such and the version is incremented with almost each new commit, but there are no explicitly tagged releases) so it's up to the maintainer to keep up and update the package accordingly, just like with any other package really.
Regarding the UT dictionary, Mozc is the open source version of Google Japanese Input, which is a top-quality Japanese IME (along the lines of Google Keyboard et al). But Mozc being open source unfortunately means that it doesn't come with the extensive dictionaries/definitions that actually make Google Japanese Input what it is, because Google has chosen to keep them as closed source (possibly to hold an advantage over its competition). So what the UT dictionary does is bring the open source Mozc (closer) to the quality of its closed source cousin by patching the bundled dictionaries and expanding them.
There are some people that for whatever reason do not seem to care for the UT dictionary (or seemingly even for plain Mozc/IBus, seeing as even this vanilla package isn't part of the official Arch repos as IMHO it should) but as I said in the previous comment, I just now realized that since in my version of the packages Mozc has been split into its own base package, ibus-mozc-ut is actually nothing more but plain old ibus-mozc - the UT part only concerns the base Mozc package. So it could be made that there is only one version each of ibus-mozc, emacs-mozc, fcitx-mozc, fcitx5-mozc etc in the AUR, and two choices for the base Mozc part: mozc and mozc-ut, both of which the individual packages would be compatible with, and so the choice would be left to the user on whether to use UT or not. This way I think everybody would be happy.
ruahcra commented on 2021-11-02 10:18 (UTC) (edited on 2021-11-02 10:21 (UTC) by ruahcra)
So both packages build from the same upstream source, but apart from the additional dictionaries they include, the only difference is that this package is stuck on a old commit, where-as ibus-mozc-ut is using a more recent commit?
Also since mozc does not tag releases then it is up to the PKGBUILD maintainer to update the package at an appropriate commit in order to keep it up to date?
In that case I hope you are successful in getting ownership of this package! I will be moving to
ibus-mozc-ut
for the time being.Nocifer commented on 2021-11-02 10:00 (UTC)
@CyberShadow Hmm, now that you mention it... There is of course the issue that my ibus-mozc-ut package includes the unofficial UT dictionary, so it's not a one for one replacement for the vanilla ibus-mozc, but since the base Mozc functionality (along with the UT inclusion) has been split into its own package, there really isn't anything that precludes merging them all into a family of interchangeable packages.
Well, back when I created my package I didn't want to step on anyone's toes (let alone @ponsfoot's, who'd been the de facto maintainer of the Mozc AUR packages for ages) but I think you're right, this probably calls for an orphan-and-adopt procedure. Thanks for the tip.
CyberShadow commented on 2021-11-02 09:43 (UTC)
Nocifer, I think the appropriate procedure for this case is to submit a request to orphan this package and adopt it. If this package provides zero benefit over existing packages, then it could also be deleted, with the better packages having provides/replaces=mozc to provide an upgrade path.
Nocifer commented on 2021-11-02 09:39 (UTC) (edited on 2021-11-02 10:58 (UTC) by Nocifer)
Hey guys, I hope you all are aware that this package was last updated some 3 years ago and is currently unmaintained and severely out of date? I'm not usually one to tout my own horn, but there does exist an updated version in the AUR that is actively maintained (currently by me; that's the proverbial horn) and which solves the issues I see mentioned here, both the dependency on gtk2 (that's been deprecated and removed by upstream since ages ago, along with the python2 dependency) and the conflict between ibus-mozc and fcitx-mozc (you can have both installed on your system at the same time).
The updated package is ibus-mozc-ut. And again, because I dislike touting my own horn, let me just say that it's not like I stand to gain something by posting this "ad" here, it's just that the whole reason I created a new package in the first place was to spare people (myself included) from exactly the kind of issues reported in the comments here.
Just a friendly FYI.
jole commented on 2021-08-21 23:36 (UTC)
please add gtk2 as a dependency? that fixed it for me aswell
Aargonian commented on 2021-03-17 00:43 (UTC)
Installing the gtk2 package resolved the build issue mentioned by @CyberShadow for me.
CyberShadow commented on 2020-12-31 20:26 (UTC)
Seems to fail finding gtk+:
Missing dependency?
npzaak commented on 2020-01-25 02:50 (UTC) (edited on 2021-02-22 14:30 (UTC) by npzaak)
@cobaltspace :
To avoid conflict with fcitx-mozc,
Option A. Modify fcitx-mozc (community) package to build mozc_emacs_helper with it.
Option B. Or, remove conflicted modules from mozc (AUR) package.
Both ways need to edit PKGBUILD by yourself.
For Option A, following posts are useful (if you can read or translate Japanese).
https://qiita.com/yutopp/items/7e042c04331b47506e95 , https://noyuno.github.io/2018-06-01-mozc
And, there is modified PKGBUILD at https://github.com/nozaki87/svntogit-community/blob/fcitx-mozc-w-emacshelper/fcitx-mozc/trunk/PKGBUILD .
You can use this PKGBUILD off-the-shelf at your own risk.
For Option B, there are good posts (also written in Japanese).
http://ain0204.hatenablog.com/entry/2016/08/12/235206 , https://qiita.com/hattorix@github/items/909df7f4bf01e57320c0
Sorry if this is off-topic...
cobaltspace commented on 2019-12-24 10:52 (UTC)
Is there a way to not conflict with fcitx-mozc?
ponsfoot commented on 2019-11-05 11:11 (UTC)
@adam900710: Emacs should not be required as deps/makedeps by default. Only required when `_emacs_mozc="yes"' is defined in PKGBUILD (uncomment line 4).
adam900710 commented on 2019-11-04 02:38 (UTC)
Can we have a PKGBUILD for guys don't care about Emacs? That dep for Emacs is pretty annoying, even just a makedep.
xuanruiqi commented on 2019-02-18 06:20 (UTC)
Sorry for this question which might be stupid. Is there a way such that I can use Mozc in both fcitx and Emacs? If I try to install the Mozc package here, then it conflicts with fcitx-mozc. But if I do not, then I cannot install emacs-mozc.
ponsfoot commented on 2019-02-04 12:06 (UTC)
@god:
I think, it's not related to mozc, related to IM framework (i.e. ibus, uim). I can input 'ろ' (` key) with Kana input mode on en_US.UTF-8 (I use ASCII layout keyboard and uim). If you set the input mode only on mozc setting, check IM framework setting.
It's a Qt5 issue, isn't it? (I don't have HiDPI monitor) Same issue has been reported in the past: https://github.com/google/mozc/issues/326
god commented on 2019-02-04 10:05 (UTC)
Thank you for your work. I have two wishes:
Could you make the Kana input mode's layout to that of Windows (en-US) or at least add an option to set it so? That is, the ` key should input ろ, not ゛, like this picture (https://i.stack.imgur.com/wPzcp.jpg). Fcitx-Mozc also works this way, but unfortunately, I could not get fcitx-mozc work on Gnome.
Could you make the Mozc Settings dialogue scale properly on high DPI Wayland, or at least make the dialogue resizeable? Currently, it looks like this: https://imgur.com/a/MXaiJcU
redboltz commented on 2018-12-01 07:59 (UTC)
Thank you! I can get the version 2.23.2815.102-3 now.
ponsfoot commented on 2018-12-01 05:54 (UTC)
@redboltz : It should be fixed now. Thank you for the feedback.
redboltz commented on 2018-12-01 04:16 (UTC) (edited on 2018-12-01 04:17 (UTC) by redboltz)
It seems that mozc version is still 2.20.2673.102-2.
I did
pacman -Syu
then
pacman -Ss mozc
got the following result:
My
/etc/pacman.conf
contains the following setting:Am I missing something?
ponsfoot commented on 2018-10-31 10:21 (UTC)
@MaxMilton: Okay. I'll move them. Please wait.
MaxMilton commented on 2018-10-30 19:35 (UTC)
Package fails to install due to SHA1 sum mismatch. Looks like instead of downloading the jigyosyo-201805.zip and x-ken-all-201805.zip files, it instead fetches the sourceforge download page. Please move your packages away from sourceforge -- GitHub etc. is be a much better option now-a-days.
ponsfoot commented on 2018-05-31 12:32 (UTC)
@MightyPork: Applied, Thank you for the patch.
MightyPork commented on 2018-05-27 10:26 (UTC) (edited on 2018-05-27 10:29 (UTC) by MightyPork)
This package does not build.
Fix by using custom.patch (fixes the build error and also enables hiragana by default, so you don't need to click in the tray menu)
https://gist.githubusercontent.com/MightyPork/6b93f56b404e526268ac133f1a783afd/raw/40b3b9569d4b0741d78c511b247b26d2b1e7a2ae/mozc.patch
and adding
patch -Np0 -i "${srcdir}/custom.patch"
at the top of prepare () {
then run updpkgsums and makepkg -f
ponsfoot commented on 2018-03-02 13:15 (UTC)
Hi,
I intend to bump latest commit of mozc (which fixes ibus-mozc issue) with latest zipcode but cannot it due to sf.net trouble. Please give me some time. I might change file hosting service.
Thx
polm23 commented on 2017-09-11 07:14 (UTC)
linkmauve commented on 2017-04-20 13:43 (UTC)
ponsfoot commented on 2017-04-16 09:59 (UTC)
eschwartz commented on 2017-04-14 17:13 (UTC)
ponsfoot commented on 2017-01-10 07:38 (UTC)
mkasu commented on 2017-01-10 05:18 (UTC)
ponsfoot commented on 2016-11-15 10:48 (UTC)
AKremlin commented on 2016-11-10 12:21 (UTC)
ponsfoot commented on 2016-10-29 08:30 (UTC) (edited on 2016-10-29 08:32 (UTC) by ponsfoot)
nash commented on 2016-10-28 22:54 (UTC)
ponsfoot commented on 2016-10-27 12:24 (UTC)
ploop commented on 2016-10-26 22:12 (UTC)
ponsfoot commented on 2015-07-18 03:39 (UTC)
k2_8191 commented on 2015-07-17 22:56 (UTC)
ponsfoot commented on 2015-05-18 15:05 (UTC)
ishitatsuyuki commented on 2015-05-18 09:01 (UTC)
nash commented on 2015-05-18 02:07 (UTC)
ponsfoot commented on 2015-05-16 08:25 (UTC)
ponsfoot commented on 2015-02-09 10:51 (UTC)
wiegraffolles commented on 2015-02-09 09:55 (UTC)
m13253 commented on 2015-01-25 14:20 (UTC)
ponsfoot commented on 2014-11-03 06:06 (UTC)
taro-k commented on 2014-10-13 06:48 (UTC)
ponsfoot commented on 2014-10-13 05:26 (UTC)
taro-k commented on 2014-10-13 03:25 (UTC)
ponsfoot commented on 2014-10-13 02:08 (UTC)
taro-k commented on 2014-10-13 01:32 (UTC)
ponsfoot commented on 2014-06-07 04:08 (UTC)
hagabaka commented on 2014-06-07 02:44 (UTC)
felixonmars commented on 2013-12-27 04:55 (UTC)
julroy67 commented on 2013-12-11 20:49 (UTC)
ponsfoot commented on 2013-05-28 07:43 (UTC) (edited on 2018-11-30 12:02 (UTC) by ponsfoot)
(repository moved)
Unofficial user repository of Mozc is ready.
If you want to use the repo, add the following into your /etc/pacman.conf
[pnsft-pur]
SigLevel = Optional TrustAll
Server = https://osdn.net/projects/ponsfoot-aur/storage/pur/x86_64
You can specify `pacman -S mozc-im' to choose all of Mozc packages.
See https://wiki.archlinux.org/index.php/Mozc for more detail.
ponsfoot commented on 2013-03-25 11:22 (UTC)
andrew67 commented on 2013-03-25 05:42 (UTC)
salviati commented on 2012-10-16 11:42 (UTC)
ponsfoot commented on 2012-05-11 15:35 (UTC)
cuihao commented on 2012-05-11 12:12 (UTC)
ponsfoot commented on 2012-03-30 10:49 (UTC)
ponsfoot commented on 2012-03-28 10:45 (UTC)
sokuban commented on 2012-03-27 02:45 (UTC)
ponsfoot commented on 2012-03-26 15:20 (UTC)
sokuban commented on 2012-03-26 14:08 (UTC)
ponsfoot commented on 2012-03-26 11:05 (UTC)
sokuban commented on 2012-03-26 05:19 (UTC)
ponsfoot commented on 2012-03-25 12:43 (UTC)
sokuban commented on 2012-03-25 08:50 (UTC)
ponsfoot commented on 2012-03-18 03:19 (UTC)
csslayer commented on 2012-03-17 16:11 (UTC)
ponsfoot commented on 2012-03-17 10:11 (UTC)
csslayer commented on 2012-03-17 07:28 (UTC)
ponsfoot commented on 2012-03-08 15:47 (UTC)
ponsfoot commented on 2012-03-08 14:20 (UTC)
ponsfoot commented on 2012-03-07 16:14 (UTC)
ponsfoot commented on 2012-02-07 12:02 (UTC)
ponsfoot commented on 2011-11-30 13:01 (UTC)
ponsfoot commented on 2011-11-30 10:37 (UTC)
myuhe commented on 2011-11-30 10:15 (UTC)
ponsfoot commented on 2011-11-30 02:06 (UTC)
myuhe commented on 2011-11-29 23:33 (UTC)
commented on 2011-10-30 11:14 (UTC)
ponsfoot commented on 2011-10-30 07:31 (UTC)
commented on 2011-10-29 16:12 (UTC)
ponsfoot commented on 2011-10-29 15:10 (UTC)
commented on 2011-10-29 14:56 (UTC)
commented on 2011-10-29 12:03 (UTC)
commented on 2011-10-29 11:36 (UTC)
ponsfoot commented on 2011-10-29 11:07 (UTC)
commented on 2011-10-29 09:37 (UTC)
ponsfoot commented on 2011-10-29 03:08 (UTC)
commented on 2011-10-28 22:19 (UTC)
ponsfoot commented on 2011-10-03 14:08 (UTC)
ponsfoot commented on 2011-08-25 10:10 (UTC)
w1ntermute commented on 2011-08-24 19:11 (UTC)
ponsfoot commented on 2011-08-23 05:43 (UTC)
w1ntermute commented on 2011-08-23 05:10 (UTC)
ponsfoot commented on 2011-08-23 04:37 (UTC)
w1ntermute commented on 2011-08-22 23:29 (UTC)
ponsfoot commented on 2011-08-22 10:24 (UTC)
ponsfoot commented on 2011-08-03 16:06 (UTC)
w1ntermute commented on 2011-08-03 13:07 (UTC)
ponsfoot commented on 2011-07-31 06:53 (UTC)
w1ntermute commented on 2011-07-31 04:39 (UTC)
ponsfoot commented on 2011-07-29 10:18 (UTC)
ponsfoot commented on 2011-04-15 15:04 (UTC)
ponsfoot commented on 2010-09-02 04:49 (UTC)
sokuban commented on 2010-09-02 01:05 (UTC)
ponsfoot commented on 2010-08-11 15:37 (UTC)
commented on 2010-08-11 14:30 (UTC)
ponsfoot commented on 2010-08-10 08:08 (UTC)