https://wiki.archlinux.org/api.php?action=feedcontributions&user=Cemsbr&feedformat=atomArchWiki - User contributions [en]2024-03-29T06:48:41ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Input_Japanese_using_uim&diff=373315Input Japanese using uim2015-05-11T03:12:07Z<p>Cemsbr: /* Sans-serif */ misspelling</p>
<hr />
<div>[[Category:Internationalization]]<br />
[[ja:Uim を使って日本語を入力]]<br />
{{Expansion|Explain how to set up other languages too.|section=UIM -- how to set up with x language}}<br />
This page explains how to get the Japanese input to work using [http://code.google.com/p/uim/ uim].<br />
<br />
If you use SCIM, see [[Smart Common Input Method platform]].<br />
<br />
If you use IBus, see [[Ibus]].<br />
<br />
== Installation ==<br />
<br />
You need the following packages to input Japanese.<br />
<br />
* Japanese fonts<br />
* Japanese input method (Kana to Kanji conversion engine)<br />
* Input method framework: uim<br />
<br />
=== Japanese fonts ===<br />
<br />
''see also [[Fonts]] and [[Font configuration]] for configuration or more detail.''<br />
<br />
Recommended Japanese fonts are as follows.<br />
==== Sans-serif ====<br />
* [https://github.com/adobe-fonts/source-han-sans adobe-source-han-sans] || {{Pkg|adobe-source-han-sans-jp-fonts}} or {{Pkg|adobe-source-han-sans-otc-fonts}}<br />
: Open-source OTF fonts developed by Adobe.<br />
<br />
==== Serif and Sans-serif ====<br />
* [http://ossipedia.ipa.go.jp/ipafont/ IPA fonts] || {{Pkg|otf-ipafont}}<br />
: An open source OTF font set including sans-serif (Gothic) and serif (Mincho) glyphs provided by Information-technology Promotion Agency, Japan (IPA).<br />
<br />
If you want to show [http://en.wikipedia.org/wiki/2channel_Shift_JIS_art 2channel Shift JIS art] properly, use one of the following fonts:<br />
* ipamona font (AUR: {{AUR|ttf-ipa-mona}})<br />
* Monapo font (AUR: {{AUR|ttf-monapo}})<br />
<br />
=== uim ===<br />
<br />
==== Using pacman ====<br />
<br />
[[pacman|Install]] {{Pkg|uim}} from the [[official repositories]].<br />
<br />
==== Compiling uim from source using PKGBUILD ====<br />
<br />
If you want to build uim with your configurationin, you can compile from source, using [[ABS]] for istance. See [http://code.google.com/p/uim/wiki/InstallUim official wiki] for all configure options.<br />
<br />
In Arch official repositories, uim is built with the following custom configuration (as of 1.8.6):<br />
* {{ic|--with-anthy-utf8}} - Enable Anthy(UTF-8) support<br />
* {{ic|--with-qt4-immodule}} - Build Qt4 immodule<br />
* {{ic|--with-qt4}} - Build uim-tools for Qt4<br />
<br />
If you want KDE4 plasma widget, install {{Pkg|automoc4}} for making dependency, and add {{ic|--enable-kde4-applet}} option to PKGBUILD file.<br />
<br />
=== Input method ===<br />
<br />
==== Anthy ====<br />
<br />
Anthy is one of the most popular Japanese input methods in the open source world. However, it has not been maintained for a long time. [http://wiki.debian.org/Teams/DebianAnthy Debian succeeds it] from May 2010.<br />
<br />
Install {{Pkg|anthy}} from the official repositories.<br />
<br />
===== Extra dictionary =====<br />
<br />
Anthy's default dictionary does not include several characters which are not specified on EUC-JP (JIS X 0208) such as "①", "♥", etc. [http://en.sourceforge.jp/projects/alt-cannadic/ alt-cannadic] provides extra dictionaries including those characters.<br />
<br />
Get [http://en.sourceforge.jp/projects/alt-cannadic/releases/?package_id=6129 alt-cannadic dictionary] and put them under your {{Ic|~/.anthy/imported_words_default.d}}.<br />
$ tar jxvf alt-cannadic-091230.tar.bz2<br />
$ mkdir ~/.anthy/imported_words_default.d (if not exist)<br />
$ cp alt-cannadic-091230/extra/*.t ~/.anthy/imported_words_default.d/<br />
<br />
Please see [http://sourceforge.jp/projects/alt-cannadic/wiki/%E4%BD%BF%E3%81%84%E6%96%B9_Anthy-UTF-8 official wiki] for more detail (Japanese).<br />
<br />
{{Warning|If you will be using this extra dictionary, choose '''Anthy (UTF-8)''' for default input method on uim.}}<br />
<br />
==== Modified Anthy (anthy-ut) ====<br />
<br />
[http://www.geocities.jp/ep3797/anthy_dict_01.html Modified Anthy] is a set of patches and huge extended dictionaries which aims to improve the Kana to Kanji conversion quality of original Anthy.<br />
<br />
Modified Anthy consists two different upstreams:<br />
* Patched source of Anthy by [http://www.fenix.ne.jp/~G-HAL/soft/nosettle/#anthy G-HAL]<br />
* Huge extended dictionalies by [http://www.geocities.jp/ep3797/anthy_dict_01.html UTSUMI]<br />
<br />
{{Warning|<br />
* Modified Anthy applies to only Anthy (UTF-8). So you have to choose '''Anthy (UTF-8)''' for default input method on uim.<br />
* Modified Anthy does not have compatibility of the dictionaries and learning data with original Anthy.<br />
}}<br />
<br />
===== Compiling modified Anthy using PKGBUILD =====<br />
<br />
Modified Anthy is available on AUR named {{AUR|anthy-ut}}.<br />
<br />
Get anthy-ut tarball and makepkg to make and install package:<br />
$ wget https://aur.archlinux.org/packages/anthy-ut/anthy-ut.tar.gz<br />
$ tar xvf anthy-ut.tar.gz<br />
$ cd anthy-ut<br />
$ makepkg -s -i<br />
<br />
If you already use original Anthy, you have to convert the existing learning data format.<br />
$ rm ~/.anthy/last-record1_*.bin<br />
$ anthy-agent --update-base-record<br />
$ rm ~/.anthy/last-record1_*.bin<br />
$ anthy-agent --update-base-record<br />
(Though this step repeats the same commands twice, it is not mistypes.)<br />
<br />
==== Anthy Kaomoji ====<br />
<br />
[http://sourceforge.jp/projects/anthy/ Anthy Kaomoji] is a modified version of Anthy that converts Hiragana text to Kana Kanji mixed text and has emoticon (顔文字) and 2ch dictionaries.<br />
It can be found in the AUR ({{AUR|anthy-kaomoji}}).<br />
<br />
==== Mozc ====<br />
<br />
''See [[Mozc]].''<br />
<br />
[http://code.google.com/p/mozc/ Mozc] is a Japanese Input Method Editor (IME) designed for multi-platform such as Chromium OS, Windows, Mac and Linux which originates from [http://www.google.com/intl/ja/ime/ Google Japanese Input].<br />
<br />
Though {{AUR|Mozc}} adapts to only ibus input method framework, [http://code.google.com/p/macuim/ macuim] provides uim-mozc plugin.<br />
<br />
===== Mozc (Vanilla) =====<br />
<br />
{{AUR|uim-mozc}} is available on AUR.<br />
{{Note|This does not support kill_line feature of uim-mozc.}}<br />
You can install this from unofficial user repository. Add the following into your /etc/pacman.conf:<br />
[pnsft-pur]<br />
SigLevel = Optional TrustAll<br />
Server = http://downloads.sourceforge.net/project/pnsft-aur/pur/$arch<br />
{{Note|This repo provides x86_64 packages only now.}}<br />
And refresh package database:<br />
# pacman -Syy<br />
You can choose install packages specifying group name as follows:<br />
# pacman -S mozc-im<br />
Or, specify package names directly. For example:<br />
# pacman -S uim-mozc<br />
<br />
===== mozc-ut and mozc-svn =====<br />
<br />
{{AUR|mozc-ut}} and {{AUR|mozc-svn}} can be built uim-mozc.<br />
{{Note|mozc-ut can work with {{AUR|uim-mozc}}.}}<br />
To build uim-mozc, edit PKGBUILD like follow, i,e. uncomment {{Ic|1=_uim_mozc=}} line:<br />
## If you will not be using ibus, comment out below.<br />
_ibus_mozc="yes"<br />
## If you will be using uim, uncomment below.<br />
_uim_mozc="yes"<br />
## If applying patch for uim-mozc fails, try to uncomment below.<br />
#_kill_kill_line="yes"<br />
## This will disable the 'kill-line' function of uim-mozc.<br />
{{Tip|If you will never be using ibus-mozc, comment out the {{Ic|1=_ibus_mozc=}} line.}}<br />
<br />
===== Registering Mozc =====<br />
<br />
{{Warning|You '''must''' run the following command whenever you upgrade or (re-)install uim.<br/><br />
# uim-module-manager --register mozc}}<br />
<br />
==== Google CGI API for Japanese input ====<br />
<br />
[http://www.google.co.jp/ime/cgiapi.html Google CGI API for Japanese Input] (Google-CGIAPI-Jp) is CGI service to provide Japanese conversion on the Internet by Google. It can be used on [http://www.google.com/transliterate web browser]. Its conversion engine seems to be equivalent to Google Japanese Input, so conversion quality is probably better than Mozc.<br />
<br />
{{Note|This service sends/receives preedits and candidates as plain text (as of 2012-09).}}<br />
<br />
You can use it via uim. Choose "Google-CGIAPI-Jp" on uim-im-switcher-gtk/gtk3/qt4 or uim-pref-gtk/gtk3/qt4.<br />
<br />
== Settings ==<br />
<br />
=== Environment variables ===<br />
<br />
Add the following to ~/.[[xprofile]], ~/.[[xinitrc]] or ~/.xsession:<br />
<br />
export GTK_IM_MODULE='uim'<br />
export QT_IM_MODULE='uim'<br />
uim-xim &<br />
export XMODIFIERS='@im=uim'<br />
<br />
{{Note|The variables should be exported before starting your desktop environment, i.e. before "exec startxfce4" or similar. [[#Using_systemd|See below]] if you're using systemd to manage your X session. }}<br />
<br />
=== Toolbar utilities ===<br />
<br />
If you want to use UimToolbar utilities which shows and controls uim mode, add '''one''' of the followings, too.<br />
<br />
==== uim-toolbar-gtk/qt ====<br />
<br />
Using toolbar appears as a window.<br />
<br />
For GTK+ 2:<br />
uim-toolbar-gtk &<br />
For GTK+ 3:<br />
uim-toolbar-gtk3 &<br />
For Qt4:<br />
uim-toolbar-qt4 &<br />
<br />
==== uim-toolbar-gtk-systray ====<br />
<br />
Using toolbar for system tray.<br />
<br />
For GTK+ 2:<br />
uim-toolbar-gtk-systray &<br />
For GTK+ 3:<br />
uim-toolbar-gtk3-systray &<br />
<br />
==== Panel applet ====<br />
<br />
Or, if you use GNOME, KDE or Xfce, you can use uim-toolbar panel applet (Xfce requires xfce4-xfapplet-plugin to use uim-applet-gnome).<br />
<br />
=== Using systemd ===<br />
<br />
If you are [[Systemd/User#Using_.2Fusr.2Flib.2Fsystemd.2Fsystemd_--user_To_Manage_Your_Session|using systemd to manage your X session]], you'll need to set the environment variables in your systemd session rather than an init script.<br />
<br />
{{hc|~/.config/systemd/user/uim-env.service|<nowiki><br />
[Unit]<br />
Description=uim environment initialization<br />
Before=xorg.target<br />
<br />
[Service]<br />
Type=oneshot<br />
ExecStart=/usr/bin/systemctl --user set-environment XMODIFIERS=@im=uim<br />
ExecStart=/usr/bin/systemctl --user set-environment GTK_IM_MODULE=uim<br />
ExecStart=/usr/bin/systemctl --user set-environment QT_IM_MODULE=uim<br />
</nowiki>}}<br />
<br />
{{hc|~/.config/systemd/user/uim.service|<nowiki><br />
[Unit]<br />
Description=uim daemon<br />
Wants=uim-env.service<br />
After=xorg.target<br />
<br />
[Service]<br />
ExecStart=/usr/bin/uim-xim<br />
Restart=on-abort<br />
<br />
[Install]<br />
WantedBy=xorg.target</nowiki><br />
}}<br />
<br />
{{hc|~/.config/systemd/user/uim-toolbar.service|<nowiki><br />
[Unit]<br />
Description=uim toolbar<br />
PartOf=uim.service<br />
<br />
[Service]<br />
ExecStart=/usr/bin/uim-toolbar-of-your-choice<br />
Restart=on-abort<br />
<br />
[Install]<br />
WantedBy=uim.service</nowiki><br />
}}<br />
<br />
Lastly, you'll need to enable the services:<br />
$ systemctl --user enable uim.service uim-toolbar.service<br />
<br />
=== uim preferences ===<br />
<br />
Configure uim preferences by running :<br />
$ uim-pref-gtk (Or, uim-pref-gtk3/uim-pref-qt4)<br />
which brings forth a GUI.<br />
<br />
Choose your preferring input method as 'Default input method'.<br />
{{Note|Mozc will be not listed in 'Default input method' at first time so you will need to add it into 'Enabled input methods' to use.}}<br />
<br />
You can run {{ic|uim-xim}} or restart X to test your settings.<br />
<br />
Provided everything went well you should be able to input Japanese in X.<br />
<br />
=== Input Japanese on Emacs ===<br />
<br />
uim provides uim.el the bridge software between Emacs and uim. Here is a sample to use uim on Emacs with utf-8 encoding. <br />
<br />
Please see [http://code.google.com/p/uim/wiki/UimEl Official wiki] for more detail.<br />
<br />
==== LEIM or minor-mode ====<br />
<br />
You can call uim.el from Emacs in two ways; directly or with the LEIM (Library of Emacs Input Method) framework. Though settings of them are different, basic functions are same. If you want to switch between uim.el and other Emacs IMs frequently, you should use LEIM framework.<br />
<br />
===== Settings for the minor-mode =====<br />
<br />
If you will be using on minor-mode, write the following settings into your {{Ic|.emacs.d/init.el}} or some other file for Emacs customizing.<br />
;; read uim.el<br />
(require 'uim)<br />
;; uncomment next and comment out previous to load uim.el on-demand<br />
;; (autoload 'uim-mode "uim" nil t)<br />
<br />
;; key-binding for activate uim (ex. C-\)<br />
(global-set-key "\C-\\" 'uim-mode)<br />
<br />
===== Settings for the LEIM =====<br />
<br />
If you will be using via LEIM, write the following settings into your {{Ic|.emacs.d/init.el}} or some other file for Emacs customizing and choose default input method.<br />
;; read uim.el with LEIM initializing<br />
(require 'uim-leim)<br />
<br />
;; set default IM. Uncomment the one of the followings.<br />
;(setq default-input-method "japanese-anthy-utf8-uim") ; Anthy (UTF-8)<br />
;(setq default-input-method "japanese-google-cgiapi-jp-uim") ; Google-CGIAPI-Jp<br />
;(setq default-input-method "japanese-mozc-uim") ; Mozc<br />
<br />
==== Preferred character encoding ====<br />
<br />
uim.el uses euc-jp character encoding by default. To set UTF-8 as preferred encodings, add the followings into your {{Ic|.emacs.d/init.el}} or some other file for Emacs customizing.<br />
;; Set UTF-8 as preferred character encoding (default is euc-jp).<br />
(setq uim-lang-code-alist<br />
(cons '("Japanese" "Japanese" utf-8 "UTF-8")<br />
(delete (assoc "Japanese" uim-lang-code-alist) <br />
uim-lang-code-alist)))<br />
<br />
==== Enable inline candidates displaying mode by default ====<br />
<br />
The inline candidates displaying mode displays conversion candidates just below (or above) preedit text vertically instead of echo area. If you want to enable inline candidates displaying mode by default, write as follows.<br />
;; set inline candidates displaying mode as default<br />
(setq uim-candidate-display-inline t)<br />
<br />
==== Set Hiragana input mode by default ====<br />
<br />
To set Hiragana input mode at activting uim, add the settings like follows:<br />
<br />
;; Set Hiragana input mode at activating uim.<br />
(setq uim-default-im-prop '("action_anthy_utf8_hiragana"<br />
"action_google-cgiapi-jp_hiragana"<br />
"action_mozc_hiragana"))<br />
<br />
==== Ignoring C-SPC on uim.el ====<br />
<br />
When you are assigning activation/deactivation of input method to C-SPC, C-SPC is stolen to switch input mode by uim.el while it is activated. To prevent the stealing and use for set-mark-command, add the followings into your {{Ic|.emacs.d/init.el}} or some other file for Emacs customizing.<br />
(add-hook 'uim-load-hook<br />
'(lambda ()<br />
(define-key uim-mode-map [67108896] nil)<br />
(define-key uim-mode-map [0] nil)))<br />
<br />
==== Disabling XIM on Emacs ====<br />
<br />
When you are using input method on your desktop and assigning activation/deactivation of input method to C-SPC, you will be not able to use C-SPC/C-@ as set-mark-command on Emacs. To avoid this problem, add the following into your {{Ic|~/.Xresources}} or {{Ic|~/.Xdefaults}}. xim will be disabled on Emacs.<br />
Emacs*UseXIM: false<br />
<br />
== Troubleshooting ==<br />
<br />
=== Set the GTK_IM_MODULE variable, but uim still not works with GTK+ 2 applications ===<br />
<br />
In case you already set the GTK_IM_MODULE environmental variable, but uim still not works with GTK+ 2 applications, you need to specify the location of gtk.immodules, which is created by and can be generated with {{Ic|gtk-query-immodules-2.0}}.<br />
<br />
The default location is {{Ic|/etc/gtk-2.0/gtk.immodules}} for GTK+ 2.<br />
<br />
You can do this with either the GTK_IM_MODULE_FILE variable (''not recommended'', it causes GTK+ 3 applications to see incompatible modules) or the im_module_file setting (''recommended'').<br />
<br />
Add the following to {{Ic|/etc/gtk-2.0/gtkrc}} or {{Ic|~/.gtkrc-2.0}}:<br />
<br />
im_module_file "/etc/gtk-2.0/gtk.immodules"<br />
<br />
=== Cannot input Japanese on Opera ===<br />
<br />
If you use Opera and cannot input Japanese with uim, try to edit environment variable as follows:<br />
Make sure to add follows in the beginning of /usr/bin/opera.<br />
<br />
export XMODIFIERS='@im=uim'<br />
export QT_IM_MODULE='xim'<br />
<br />
=== Cannot type a consonant in Zenkaku mode ===<br />
<br />
If you cannot type a consonant in Zenkaku mode, add follows to your config file.<br />
<br />
e.g. vi ~/.uim.d/customs/custom-google-cgiapi-jp.scm<br />
<br />
(define ja-rk-rule-hoge<br />
(map<br />
(lambda (c)<br />
(list (cons (list c) ()) (list c c c)))<br />
'("b" "c" "d" "f" "g" "h" "j" "k" "l" "m"<br />
"p" "q" "r" "s" "t" "v" "w" "x" "y" "z"<br />
"A" "B" "C" "D" "E" "F" "G" "H" "I" "J" "K" "L" "M"<br />
"N" "O" "P" "Q" "R" "S" "T" "U" "V" "W" "X" "Y" "Z")))<br />
(if (symbol-bound? 'ja-rk-rule-hoge)<br />
(set! ja-rk-rule (append ja-rk-rule-hoge ja-rk-rule)))<br />
<br />
=== uim-toolbar-gtk-systray: tray icon is crushed ===<br />
<br />
Though some of DE, WM or panel application may provide only one icon space per application on system-tray/notification-area, uim-toolbar-gtk-systray displays some icons on it by default so those icons are crushed. Choose just one of them to solve it. The steps to display only 'Input mode' icon for example as follows:<br />
# Run {{Ic|uim-pref-gtk}}.<br />
# Click 'Toolbar' on 'Group' list.<br />
# Take the all checkmarks off.<br />
# Click 'Anthy', 'Anthy (UTF-8)' or 'Mozc' which you are using on 'Group' list.<br />
# Click Edit button in 'Toolbar' box > 'Enable toolbar buttons' line.<br />
# Enable only 'Input mode' and click 'Close' button.<br />
# Click 'OK' button to close uim-pref-gtk.<br />
The tray icon will be displayed "あ" (Hiragana mode) or "ー" (Direct mode).<br />
<br />
=== I use darker theme, I cannot read the uim mode icons ===<br />
<br />
You can choose icons for darker background (uim 1.6.0 or later).<br />
# Run uim-perf-gtk<br />
# Click 'Toolbar' on 'Group' list.<br />
# Check 'Use icon for dark background'.<br />
<br />
== See also ==<br />
<br />
;uim<br />
:[http://code.google.com/p/uim/wiki/OfficialUserDocument uim official document]<br />
:[http://en.wikibooks.org/wiki/Uim uim on wikibooks]<br />
<br />
;Fonts<br />
:[http://www.geocities.jp/ep3797/japanese_fonts.html Japanese fonts showcase]<br />
:[http://www.geocities.jp/ep3797/modified_fonts_01.html modified Japanese fonts]</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Localization/Japanese&diff=373314Localization/Japanese2015-05-11T03:04:00Z<p>Cemsbr: /* Sans-serif */</p>
<hr />
<div>[[category:Internationalization]]<br />
{{Related articles start}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
This document provides instructions on how to set up a Japanese language environment on an Arch linux installation. This document will not cover setting up Japanese input on the console. <br />
<br />
==Fonts==<br />
<br />
''see also [[Fonts]] and [[Font configuration]] for configuration or more detail.''<br />
<br />
To use any Japanese input method, you need to have Japanese fonts installed.<br />
<br />
Recommended Japanese fonts are as follows.<br />
<br />
==== Sans-serif ====<br />
* [https://github.com/adobe-fonts/source-han-sans adobe-source-han-sans] || {{Pkg|adobe-source-han-sans-jp-fonts}} or {{Pkg|adobe-source-han-sans-otc-fonts}}<br />
: Open-source OTF fonts developed by Adobe.<br />
<br />
==== Serif (and Sans-serif) ====<br />
* [http://ossipedia.ipa.go.jp/ipafont/ IPA fonts] || {{Pkg|otf-ipafont}}<br />
: An open source OTF font set including sans-serif (Gothic) and serif (Mincho) glyphs provided by Information-technology Promotion Agency, Japan (IPA).<br />
<br />
If you want to show [http://en.wikipedia.org/wiki/2channel_Shift_JIS_art 2channel Shift JIS art] properly, use one of the following fonts:<br />
* ipamona font (AUR: {{AUR|ttf-ipa-mona}})<br />
* Monapo font (AUR: {{AUR|ttf-monapo}})<br />
<br />
== Locale ==<br />
<br />
''See [[locale]] for detail''<br />
<br />
You should have {{ic|ja_JP.UTF-8}} enabled in {{ic|/etc/locale.gen}}.<br />
<br />
==Input in Xorg==<br />
<br />
===Input Method Framework===<br />
<br />
Input method (IM) frameworks act as frontends to various input methods and libraries, allowing the user to switch between different languages with ease.<br />
<br />
You can use the following frameworks:<br />
* [[Fcitx]]<br />
* [[IBus]]<br />
* [[uim]]<br />
<br />
See each articles for detail.<br />
<br />
{{Note|[[Smart Common Input Method platform|SCIM]] is dead project. You should not use it.}}<br />
<br />
===Input method===<br />
<br />
====Mozc====<br />
<br />
''Available IM Frameworks: Fcitx, IBus, uim''<br />
<br />
''See [[Mozc]]''<br />
<br />
[http://code.google.com/p/mozc/ Mozc] is a Japanese Input Method Editor (IME) designed for multi-platform such as Chromium OS, Windows, Mac and Linux which originates from [http://www.google.com/intl/ja/ime/ Google Japanese Input].<br />
<br />
Custom package {{AUR|mozc-ut}} comes with [http://www.geocities.jp/ep3797/mozc_01.html Mozc UT dictionary]. The dictionary adds over 350,000 words into original.<br />
<br />
====libkkc====<br />
<br />
''Available IM Frameworks: Fcitx, IBus''<br />
<br />
[https://bitbucket.org/libkkc/ libkkc] provides a converter from Japanese Kana-string to Kana-Kanji-mixed-string. It was named after kkc.el in GNU Emacs, a simple Kana Kanji converter, while libkkc tries to convert sentences in a bit more complex way using N-gram language models. It is developed by a Red Hat engineer.<br />
<br />
Install {{Pkg|fcitx-libkkc}}{{Broken package link|package not found}} (for Fcitx) or {{Pkg|ibus-libkkc}}{{Broken package link|package not found}} (for IBus).<br />
<br />
====SKK====<br />
<br />
''Available IM Frameworks: Fcitx, IBus, uim''<br />
<br />
[http://openlab.jp/skk/index.html SKK] (Simple Kana to Kanji conversion program) is a Japanese input method on Emacs. It was designed by Dr. Masahiko Sato (Professor Emeritus, Kyoto University) (old link) and created in 1987. A unique feature of SKK is that it converts words one by one (single-word conversion), without analyzing syntax or grammar.<br />
<br />
Install {{Pkg|skk-jisyo}} and {{Pkg|fcitx-skk}} (for Fcitx) or {{Pkg|ibus-skk}} (for IBus). uim supports SKK itself.<br />
<br />
==== Google CGI API for Japanese input ====<br />
<br />
''Available IM Framewworks: uim''<br />
<br />
[http://www.google.co.jp/ime/cgiapi.html Google CGI API for Japanese Input] (Google-CGIAPI-Jp) is CGI service to provide Japanese conversion on the Internet by Google. It can be used on [http://www.google.com/transliterate web browser]. Its conversion engine seems to be equivalent to Google Japanese Input, so conversion quality is probably better than Mozc.<br />
<br />
{{Note|This service sends/receives preedits and candidates as plain text (as of 2012-09).}}<br />
<br />
You can use it via uim. Choose "Google-CGIAPI-Jp" on uim-im-switcher-gtk/gtk3/qt4 or uim-pref-gtk/gtk3/qt4.<br />
<br />
====Anthy====<br />
<br />
Anthy is factually dead project.</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Localization/Japanese&diff=373313Localization/Japanese2015-05-11T03:03:31Z<p>Cemsbr: /* Sans-serif */ misspelling</p>
<hr />
<div>[[category:Internationalization]]<br />
{{Related articles start}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
This document provides instructions on how to set up a Japanese language environment on an Arch linux installation. This document will not cover setting up Japanese input on the console. <br />
<br />
==Fonts==<br />
<br />
''see also [[Fonts]] and [[Font configuration]] for configuration or more detail.''<br />
<br />
To use any Japanese input method, you need to have Japanese fonts installed.<br />
<br />
Recommended Japanese fonts are as follows.<br />
<br />
==== Sans-serif ====<br />
* [https://github.com/adobe-fonts/source-han-sans adobe-source-han-sans] || {{Pkg|adobe-source-han-sans-jp-fonts}} or {{Pkg|adobe-source-han-sans-otc-fonts}}<br />
: An open source OTF fonts developed by Adobe.<br />
<br />
==== Serif (and Sans-serif) ====<br />
* [http://ossipedia.ipa.go.jp/ipafont/ IPA fonts] || {{Pkg|otf-ipafont}}<br />
: An open source OTF font set including sans-serif (Gothic) and serif (Mincho) glyphs provided by Information-technology Promotion Agency, Japan (IPA).<br />
<br />
If you want to show [http://en.wikipedia.org/wiki/2channel_Shift_JIS_art 2channel Shift JIS art] properly, use one of the following fonts:<br />
* ipamona font (AUR: {{AUR|ttf-ipa-mona}})<br />
* Monapo font (AUR: {{AUR|ttf-monapo}})<br />
<br />
== Locale ==<br />
<br />
''See [[locale]] for detail''<br />
<br />
You should have {{ic|ja_JP.UTF-8}} enabled in {{ic|/etc/locale.gen}}.<br />
<br />
==Input in Xorg==<br />
<br />
===Input Method Framework===<br />
<br />
Input method (IM) frameworks act as frontends to various input methods and libraries, allowing the user to switch between different languages with ease.<br />
<br />
You can use the following frameworks:<br />
* [[Fcitx]]<br />
* [[IBus]]<br />
* [[uim]]<br />
<br />
See each articles for detail.<br />
<br />
{{Note|[[Smart Common Input Method platform|SCIM]] is dead project. You should not use it.}}<br />
<br />
===Input method===<br />
<br />
====Mozc====<br />
<br />
''Available IM Frameworks: Fcitx, IBus, uim''<br />
<br />
''See [[Mozc]]''<br />
<br />
[http://code.google.com/p/mozc/ Mozc] is a Japanese Input Method Editor (IME) designed for multi-platform such as Chromium OS, Windows, Mac and Linux which originates from [http://www.google.com/intl/ja/ime/ Google Japanese Input].<br />
<br />
Custom package {{AUR|mozc-ut}} comes with [http://www.geocities.jp/ep3797/mozc_01.html Mozc UT dictionary]. The dictionary adds over 350,000 words into original.<br />
<br />
====libkkc====<br />
<br />
''Available IM Frameworks: Fcitx, IBus''<br />
<br />
[https://bitbucket.org/libkkc/ libkkc] provides a converter from Japanese Kana-string to Kana-Kanji-mixed-string. It was named after kkc.el in GNU Emacs, a simple Kana Kanji converter, while libkkc tries to convert sentences in a bit more complex way using N-gram language models. It is developed by a Red Hat engineer.<br />
<br />
Install {{Pkg|fcitx-libkkc}}{{Broken package link|package not found}} (for Fcitx) or {{Pkg|ibus-libkkc}}{{Broken package link|package not found}} (for IBus).<br />
<br />
====SKK====<br />
<br />
''Available IM Frameworks: Fcitx, IBus, uim''<br />
<br />
[http://openlab.jp/skk/index.html SKK] (Simple Kana to Kanji conversion program) is a Japanese input method on Emacs. It was designed by Dr. Masahiko Sato (Professor Emeritus, Kyoto University) (old link) and created in 1987. A unique feature of SKK is that it converts words one by one (single-word conversion), without analyzing syntax or grammar.<br />
<br />
Install {{Pkg|skk-jisyo}} and {{Pkg|fcitx-skk}} (for Fcitx) or {{Pkg|ibus-skk}} (for IBus). uim supports SKK itself.<br />
<br />
==== Google CGI API for Japanese input ====<br />
<br />
''Available IM Framewworks: uim''<br />
<br />
[http://www.google.co.jp/ime/cgiapi.html Google CGI API for Japanese Input] (Google-CGIAPI-Jp) is CGI service to provide Japanese conversion on the Internet by Google. It can be used on [http://www.google.com/transliterate web browser]. Its conversion engine seems to be equivalent to Google Japanese Input, so conversion quality is probably better than Mozc.<br />
<br />
{{Note|This service sends/receives preedits and candidates as plain text (as of 2012-09).}}<br />
<br />
You can use it via uim. Choose "Google-CGIAPI-Jp" on uim-im-switcher-gtk/gtk3/qt4 or uim-pref-gtk/gtk3/qt4.<br />
<br />
====Anthy====<br />
<br />
Anthy is factually dead project.</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Intel_graphics&diff=369549Intel graphics2015-04-14T08:36:15Z<p>Cemsbr: /* Tips and tricks */ Solving VLC VDPAU failure message</p>
<hr />
<div>[[Category:Graphics]]<br />
[[Category:X Server]]<br />
[[cs:Intel]]<br />
[[de:Intel]]<br />
[[es:Intel]]<br />
[[fr:Intel]]<br />
[[hu:Intel]]<br />
[[it:Intel]]<br />
[[ja:Intel Graphics]]<br />
[[pl:Intel]]<br />
[[ru:Intel graphics]]<br />
[[zh-CN:Intel Graphics]]<br />
[[zh-TW:Intel]]<br />
{{Related articles start}}<br />
{{Related|Intel GMA3600}}<br />
{{Related|Poulsbo}}<br />
{{Related|Xorg}}<br />
{{Related|Kernel mode setting}}<br />
{{Related|Xrandr}}<br />
{{Related|Hybrid graphics}}<br />
{{Related articles end}}<br />
<br />
Since Intel provides and supports open source drivers, Intel graphics are now essentially plug-and-play.<br />
<br />
For a comprehensive list of Intel GPU models and corresponding chipsets and CPUs, see [[Wikipedia:Comparison of Intel graphics processing units|this comparison on Wikipedia]].<br />
<br />
{{Note|PowerVR-based graphics ([[Poulsbo|GMA 500]] and [[Intel GMA3600|GMA 3600]] series) are not supported by open source drivers.}}<br />
<br />
== Installation ==<br />
<br />
Prerequisite: [[Xorg]].<br />
<br />
[[pacman|Install]] the {{Pkg|xf86-video-intel}} package from the [[official repositories]]. It provides the DDX driver for 2D acceleration and it pulls in {{Pkg|mesa}} as a dependency, providing the DRI driver for 3D acceleration.<br />
<br />
To enable OpenGL support, also install {{Pkg|mesa-libgl}}. If you are on x86_64 and need 32-bit support, also install {{Pkg|lib32-mesa-libgl}} from the [[multilib]] repository.<br />
<br />
Install the [[VA-API]] driver and library provided by the {{Pkg|libva-intel-driver}} and {{Pkg|libva}} packages respectively. On older GPUs, this is provided instead by the [[XvMC]] driver, which is included with the DDX driver.<br />
<br />
== Configuration ==<br />
<br />
There is no need for any configuration to run [[X]].<br />
<br />
For the full list of options, see {{ic|$ man intel}}.<br />
<br />
== Loading ==<br />
<br />
The Intel kernel module should load fine automatically on system boot.<br />
<br />
If it does not happen, then:<br />
<br />
* Make sure you do '''not''' have {{ic|nomodeset}} or {{ic|1=vga=}} as a [[Kernel parameters|kernel parameter]], since Intel requires kernel mode-setting.<br />
* Also, check that you have not disabled Intel by using any modprobe blacklisting within {{ic|/etc/modprobe.d/}} or {{ic|/usr/lib/modprobe.d/}}.<br />
<br />
=== Enable early KMS ===<br />
<br />
{{Tip|If you have problems with the resolution, you can check whether [[Kernel Mode Setting#Forcing modes and EDID|enforcing the mode]] helps.}}<br />
<br />
[[KMS|Kernel Mode Setting]] (KMS) is supported by Intel chipsets that use the i915 DRM driver and is mandatory and enabled by default. <br />
<br />
KMS is typically initialized after the [[Arch boot process#initramfs|initramfs stage]]. It is possible, however, to enable KMS during the initramfs stage. To do this, add the {{ic|i915}} module to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}:<br />
<br />
MODULES="... i915 ..."<br />
<br />
{{Tip|<br />
Users might need to add {{Ic|intel_agp}} before {{Ic|i915}} to suppress the ACPI errors. The order matters because the modules are activated in sequence.}}<br />
<br />
If you are using a custom [[Wikipedia:Extended display identification data|EDID]] file, you should embed it into initramfs as well:<br />
<br />
{{hc|/etc/mkinitcpio.conf|<br />
2=FILES="/lib/firmware/edid/your_edid.bin"}}<br />
<br />
Now, regenerate the initramfs:<br />
<br />
# mkinitcpio -p linux<br />
<br />
The change takes effect at the next reboot.<br />
<br />
== Module-based Powersaving Options ==<br />
<br />
The {{ic|i915}} kernel module allows for configuration via [[Kernel modules#Setting module options|module options]]. Some of the module options impact power saving.<br />
<br />
A list of all options along with short descriptions and default values can be generated with the following command:<br />
<br />
$ modinfo -p i915<br />
<br />
To check which options are currently enabled, run<br />
<br />
# systool -m i915 -av<br />
<br />
You will note that the {{ic|i915.powersave}} option which "enable[s] powersavings, fbc, downclocking, etc." is enabled by default, resulting in per-chip powersaving defaults. It is however possible to configure more aggressive powersaving by using [[Kernel modules#Setting module options|module options]].<br />
<br />
{{Warning|1=Diverting from the defaults will mark the kernel as [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fc9740cebc3ab7c65f3c5f6ce0caf3e4969013ca tainted] from Linux 3.18 onwards. This basically implies using other options than the per-chip defaults is considered experimental and not supported by the developers. }}<br />
<br />
The following set of options should be generally safe to enable:<br />
<br />
{{hc|/etc/modprobe.d/i915.conf|<nowiki><br />
options i915 enable_rc6=1 enable_fbc=1 lvds_downclock=1<br />
</nowiki>}}<br />
<br />
You can experiment with higher values for {{ic|enable_rc6}}, but your GPU may not support them or the activation of the other options [https://wiki.archlinux.org/index.php?title=Talk:Intel_Graphics&oldid=327547#Kernel_Module_options].<br />
<br />
Framebuffer compression, for example, may be unreliable or unavailable on Intel GPU generations before Sandy Bridge (generation 6). This results in messages logged to the system journal similar to this one:<br />
kernel: drm: not enough stolen space for compressed buffer, disabling.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Disable Vertical Synchronization (VSYNC) ===<br />
The intel-driver uses [http://www.intel.com/support/graphics/sb/CS-004527.htm Triple Buffering] for vertical synchronization, this allows for full performance and avoids tearing. To turn vertical synchronization off (e.g. for benchmarking) use this {{ic|.drirc}} in your home directory:<br />
<br />
{{hc|~/.drirc|<br />
<device screen&#61;"0" driver&#61;"dri2"><br />
<application name&#61;"Default"><br />
<option name&#61;"vblank_mode" value&#61;"0"/><br />
</application><br />
</device>}}<br />
<br />
Do not use {{Pkg|driconf}} to create this file, it is buggy and will set the wrong driver.<br />
<br />
=== Setting scaling mode ===<br />
<br />
This can be useful for some full screen applications:<br />
<br />
$ xrandr --output LVDS1 --set PANEL_FITTING param<br />
<br />
where {{ic|param}} can be:<br />
<br />
* {{ic|center}}: resolution will be kept exactly as defined, no scaling will be made,<br />
* {{ic|full}}: scale the resolution so it uses the entire screen or<br />
* {{ic|full_aspect}}: scale the resolution to the maximum possible but keep the aspect ratio.<br />
<br />
If it does not work, try:<br />
<br />
$ xrandr --output LVDS1 --set "scaling mode" param<br />
<br />
where {{ic|param}} is one of {{ic|"Full"}}, {{ic|"Center"}} or {{ic|"Full aspect"}}.<br />
<br />
=== KMS Issue: console is limited to small area ===<br />
<br />
One of the low-resolution video ports may be enabled on boot which is causing the terminal to utilize a small area of the screen. To fix, explicitly disable the port with an i915 module setting with {{ic|1=video=SVIDEO-1:d}} in the kernel command line parameter in the bootloader. See [[Kernel parameters]] for more info.<br />
<br />
If that does not work, try disabling TV1 or VGA1 instead of SVIDEO-1.<br />
<br />
=== H.264 decoding on GMA 4500 ===<br />
<br />
The {{Pkg|libva-intel-driver}} package provides MPEG-2 decoding only for GMA 4500 series GPUs. The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing {{AUR|libva-intel-driver-g45-h264}} package, available in the [[Arch User Repository]]. Note however that this support is experimental and not currently in active development. Using the VA-API with this driver on a GMA 4500 series GPU will offload the CPU but may not result in as smooth a playback as non-accelerated playback. Tests using mplayer showed that using vaapi to play back an H.264 encoded 1080p video halved the CPU load (compared to the XV overlay) but resulted in very choppy playback, while 720p worked reasonably well [https://bbs.archlinux.org/viewtopic.php?id=150550]. This is echoed by other experiences [http://www.emmolution.org/?p=192&cpage=1#comment-12292].<br />
<br />
=== Setting brightness and gamma ===<br />
<br />
The following example demonstrates using using the {{ic|/sys}} [[Wikipedia:Virtual file system|virtual file system]] to set brightness at the driver level. The maximum brightness is indicated in the file {{ic|/sys/class/backlight/intel_backlight/max_brightness}}. Note that its value may differ across different hardware configurations.<br />
<br />
{{bc|<br />
# cd /sys/class/backlight/intel_backlight<br />
# cat max_brightness<br />
4437<br />
# echo 2200 > brightness<br />
}}<br />
<br />
Brightness can alternatively be set using the {{Pkg|xorg-xbacklight}} package.<br />
<br />
$ xbacklight -set 50 # sets brightness to 50% of maximum<br />
<br />
Increments can be used instead of absolute values, for example:<br />
<br />
$ xbacklight -inc 10 # increase brightness by 10%<br />
$ xbacklight -dec 10 # decrease brightness by 10%<br />
<br />
Gamma can be set using either the {{Pkg|xorg-xrandr}} or {{Pkg|xorg-xgamma}} package. The following commands create the same effect.<br />
<br />
$ xrandr --output LVDS1 --gamma 1.0:1.0:1.0<br />
$ xgamma -rgamma 1 -ggamma 1 -bgamma 1<br />
<br />
=== VLC ===<br />
By changing some VLC preferences, you can fix the following message:<br />
<br />
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or director<br />
<br />
In ''Tools'', ''Preferences'', ''Video'' tab (v2.2.0 menu) select "OpenGL video output (experimental)" for ''Output'' and, in ''Input/Codecs'', "VA-API video decoder via X11/DRM" (both are OK) in ''Hardware-accelerated decoding'' (''Codecs'' group).[https://bugs.archlinux.org/task/44569]<br />
<br />
== Troubleshooting ==<br />
<br />
=== SNA issues ===<br />
From {{ic|man 4 intel}}:<br />
:''There are a couple of backends available for accelerating the DDX. "UXA" (Unified Acceleration Architecture) is the mature backend that was introduced to support the GEM driver model. It is in the process of being superseded by "SNA" (Sandybridge's New Acceleration). Until that process is complete, the ability to choose which backend to use remains for backwards compatibility.''<br />
<br />
''SNA'' is the default acceleration method in {{Pkg|xf86-video-intel}}. If you are experience issues with ''SNA'', try using ''UXA'' instead, which can be done by creating an [[X]] configuration file containing the following:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "uxa"<br />
EndSection<br />
}}<br />
<br />
=== Blank screen during boot, when "Loading modules" ===<br />
<br />
If using "late start" KMS and the screen goes blank when "Loading modules", it may help to add {{ic|i915}} and {{ic|intel_agp}} to the initramfs. See [[Kernel_mode_setting#Early_KMS_start]] section.<br />
<br />
Alternatively, appending the following [[Kernel parameters|kernel parameter]] seems to work as well:<br />
<br />
video=SVIDEO-1:d<br />
<br />
If you need to output to VGA then try this:<br />
<br />
video=VGA-1:1280x800<br />
<br />
=== Tear-free video ===<br />
<br />
The SNA acceleration method causes tearing for some people. To fix this, enable the {{ic|"TearFree"}} option in the driver:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "TearFree" "true"<br />
EndSection}}<br />
<br />
See the [https://bugs.freedesktop.org/show_bug.cgi?id=37686 original bug report] for more info.<br />
<br />
{{Note|<br />
* This option may not work when {{ic|SwapbuffersWait}} is {{ic|false}}.<br />
* This option is problematic for applications that are very picky about vsync timing, like [[Wikipedia:Super Meat Boy|Super Meat Boy]].<br />
* This option does not work with UXA acceleration method, only with SNA.<br />
}}<br />
<br />
=== X freeze/crash with intel driver ===<br />
<br />
Some issues with X crashing, GPU hanging, or problems with X freezing, can be fixed by disabling the GPU usage with the {{ic|NoAccel}} option:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "NoAccel" "True"<br />
EndSection}}<br />
<br />
Alternatively, try to disable the 3D acceleration only with the {{ic|DRI}} option:<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "DRI" "False"<br />
EndSection}}<br />
<br />
If you experience crashes and have<br />
<br />
Option "TearFree" "true"<br />
Option "AccelMethod" "sna"<br />
<br />
in your config file, in most cases these can be fixed by adding<br />
<br />
i915.semaphores=1<br />
<br />
to your boot parameters.<br />
<br />
=== Adding undetected resolutions ===<br />
<br />
This issue is covered on the [[Xrandr#Adding undetected resolutions|Xrandr page]].<br />
<br />
=== Weathered colors (color range problem) ===<br />
<br />
{{Note|This problem is related to the [http://lists.freedesktop.org/archives/dri-devel/2013-January/033576.html changes] in the kernel 3.9. This problem still remains in kernel 3.18}}<br />
Kernel 3.9 contains a new default "Automatic" mode for the "Broadcast RGB" property in the Intel driver. It is almost equivalent to "Limited 16:235" (instead of the old default "Full") whenever an HDMI/DP output is in a [http://raspberrypi.stackexchange.com/questions/7332/what-is-the-difference-between-cea-and-dmt CEA mode]. If a monitor does not support signal in limited color range, it will cause weathered colors.<br />
<br />
{{Note|Some monitors/TVs support both color range. In that case an option often known as ''Black Level'' may need to be adjusted to make them handle the signal correctly.}}<br />
<br />
One can force mode e.g. {{ic|xrandr --output <HDMI> --set "Broadcast RGB" "Full"}} (replace {{ic|<HDMI>}} with the appropriate output device, verify by running {{ic|xrandr}}). You can add it into your {{ic |.xprofile}}, make it executable to run the command before it will start the graphical mode.<br />
<br />
{{Note|Some TVs can handle signal in limited range only. Setting Broadcast RGB to "Full" will cause color clipping. You may need to set it to "Limited 16:235" manually to avoid the clipping.}}<br />
<br />
Also there are other related problems which can be fixed editing GPU registers. More information can be found [http://lists.freedesktop.org/archives/intel-gfx/2012-April/016217.html] and [http://github.com/OpenELEC/OpenELEC.tv/commit/09109e9259eb051f34f771929b6a02635806404c].<br />
<br />
Unfortunately, the Intel driver does not support setting the color range through an {{ic|xorg.conf.d}} configuration file.<br />
<br />
A [https://bugzilla.kernel.org/show_bug.cgi?id=94921 bug report] is filed and a patch can be found in the attachment.<br />
<br />
=== Backlight is not adjustable===<br />
After resuming from suspend, the hotkeys for changing the screen brightness do not take effect. Using the following kernel parameters can potentially solve the problem.<br />
<br />
acpi_backlight=vendor<br />
<br />
Either in addition to the above mentioned parameter, or on its own, add one of the following two parameters:<br />
acpi_osi=Linux<br />
acpi_osi="!Windows 2012"<br />
<br />
Another parameter available:<br />
video.use_native_backlight=1<br />
<br />
If neither of those solve the problem, edit or create {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "card0"<br />
Driver "intel"<br />
Option "Backlight" "intel_backlight"<br />
BusID "PCI:0:2:0"<br />
<br />
EndSection}}<br />
<br />
If using the UXA acceleration as mentioned above, create the file as follows:<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "card0"<br />
Driver "intel"<br />
Option "AccelMethod" "uxa"<br />
Option "Backlight" "intel_backlight"<br />
BusID "PCI:0:2:0"<br />
<br />
EndSection}}<br />
<br />
=== Disabling frame buffer compression ===<br />
<br />
On some cards such as Intel Corporation Mobile 4 Series Chipsets, enabling frame buffer compression results in endless error messages:<br />
<br />
$ dmesg |tail <br />
[ 2360.475430] [drm] not enough stolen space for compressed buffer (need 4325376 bytes), disabling<br />
[ 2360.475437] [drm] hint: you may be able to increase stolen memory size in the BIOS to avoid this<br />
<br />
The solution is to disable frame buffer compression which will slightly increase power consumption. In order to disable it add {{ic|i915.enable_fbc&#61;0}} to the kernel line parameters. More information on the results of disabled compression can be found [http://zinc.canonical.com/~cking/power-benchmarking/background-colour-and-framebuffer-compression/results.txt here].<br />
<br />
=== Corruption/Unresponsiveness in Chromium and Firefox ===<br />
<br />
If you experience corruption or unresponsiveness in Chromium and/or Firefox [[#SNA issues|set the AccelMethod to "uxa"]]<br />
<br />
== See also ==<br />
<br />
* https://01.org/linuxgraphics/documentation (includes a list of supported hardware)</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Talk:Gapless_Audio_CD_Creation_from_MP3s&diff=99136Talk:Gapless Audio CD Creation from MP3s2010-03-06T04:15:58Z<p>Cemsbr: </p>
<hr />
<div>This method is certainly not gapless, using LAME for decoding does not produce gapless results (though LAME does gapless encoding).<br />
<br />
Is the Table of Contents in a file named "toc" under "wav" folder and the cdrdao run there?</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Apache_HTTP_Server/mod_fcgid&diff=96314Apache HTTP Server/mod fcgid2010-02-11T22:48:39Z<p>Cemsbr: /* Step 1: Installation */</p>
<hr />
<div>{{Poor_writing}}<br />
<br />
[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Apache_and_FastCGI}}<br />
{{i18n_entry|Español|Apache_y_FastCGI_(Español)}}<br />
{{i18n_links_end}}<br />
<br />
==Introduction==<br />
There are two FastCGI modules for Apache:<br />
* [http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html mod_fastcgi] (seems to be faster; see [http://blog.chty.org/post/2007/10/08/151-apache2-mod_fcgid-vs-mod_fastcgi])<br />
* [http://fastcgi.coremail.cn/index.htm mod_fcgid]<br />
They both have permissive licenses (custom for mod_fastcgi and GPL for mod_fcgid) and they are both available in [[AUR]].<br />
<br />
==mod_fastcgi==<br />
===Step 1: Installation===<br />
[http://aur.archlinux.org/packages.php?ID=1032 mod_fastcgi] is available in [[AUR]]<br />
<br />
===Step 2: Configuration===<br />
First you need to load the fastcgi module. Make sure that the following is '''present''' and '''uncommented''' in your httpd.conf:<br />
LoadModule fastcgi_module modules/mod_fastcgi.so<br />
<br />
Then you need to tell Apache when to use FastCGI.<br />
<br />
For example you can ask Apache to treat all .fcgi files as fastcgi applications:<br />
<IfModule fastcgi_module><br />
AddHandler fastcgi-script .fcgi # you can put whatever extension you want<br />
</IfModule><br />
Remember that standard CGI restrictions apply, files must be in an ExecCGI enabled directory to execute.<br />
<br />
==mod_fcgid==<br />
===Step 1: Installation===<br />
pacman -S mod_fastcgi<br />
<br />
===Step 2: Configuration===<br />
First you need to load the fastcgi module. Make sure that the following is '''present''' and '''uncommented''' in your httpd.conf:<br />
LoadModule fcgid_module modules/mod_fcgid.so<br />
<br />
Then you need to tell Apache when to use FastCGI.<br />
<br />
For example you can ask Apache to treat all .fcgi files as fastcgi applications:<br />
<IfModule fcgid_module><br />
AddHandler fcgid-script .fcgi # you can put whatever extension you want<br />
</IfModule><br />
Remember that standard CGI restrictions apply, files must be in an ExecCGI enabled directory to execute.<br />
<br />
==Troubleshooting==<br />
It doesn't work? Apache error log (<code>/var/log/httpd/error_log</code>) should help you find the problem.<br />
<br />
==See also==<br />
*[[lighttpd and FastCGI]]</div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Nouveau&diff=82331Nouveau2009-11-07T17:20:03Z<p>Cemsbr: /* DualHead */</p>
<hr />
<div>[[Category: Graphics (English)]][[Category: X Server (English)]][[Category: HOWTOs (English)]]<br />
[http://nouveau.freedesktop.org/wiki/ Nouveau] is an open source graphic driver for nVidia cards.<br />
Don't forget to check out the [http://nouveau.freedesktop.org/wiki/FAQ FAQ] if you have any questions, there is a lot of valuable information there.<br />
<br />
== Installation ==<br />
<br />
Before proceeding, have a look at the [http://nouveau.freedesktop.org/wiki/FeatureMatrix FeatureMatrix] to see what features are supported for a given architecture, and the list of [http://nouveau.freedesktop.org/wiki/CodeNames codenames] to determine the card's category.<br />
<br />
<br />
Install the following packages :<br />
# pacman -S nouveau-drm xf86-video-nouveau<br />
<br />
== Configuration ==<br />
<br />
You can use the following xorg.conf, which allows you to easily switch back to other drivers :<br />
<br />
Section "Device"<br />
Identifier "nvidia"<br />
Driver "nouveau"<br />
#Driver "nv"<br />
#Driver "nvidia"<br />
EndSection<br />
<br />
== KMS ==<br />
<br />
Kernel Mode-Setting is a technology that puts the work of setting graphics output modes in kernel space. This allows for a cleaner implementation, and means that switching VTs (Ctrl+Alt+F1, etc.) is nearly instant. As well, you will have a full-resolution framebuffer, which is nice for high-res displays in console mode.<br />
<br />
Upstream actually recommends testing KMS as it is the future. See the [http://nouveau.freedesktop.org/wiki/KernelModeSetting KernelModeSetting] page for more information.<br />
<br />
=== Late start ===<br />
<br />
With this choice, KMS will be enabled when the boot process says, "Loading modules." This may cause an undesirable screen flicker as the mode changes right then.<br />
<br />
1) Add the following line to /etc/modprobe.d/modprobe.conf:<br />
options nouveau modeset=1<br />
<br />
2) Remove all "vga=" and "video=" options from your kernel commandline in /boot/grub/menu.lst. Using other framebuffer drivers (such as uvesafb) will conflict with KMS.<br />
<br />
=== Early start ===<br />
<br />
This method will start KMS as early as possible in the boot process, when the initramfs is loaded. Here's how to do this with the official packages:<br />
<br />
1) Add the following line to /etc/modprobe.d/modprobe.conf:<br />
options nouveau modeset=1<br />
<br />
2) Add "nouveau" to the MODULES array in /etc/mkinitcpio.conf:<br />
MODULES="'''nouveau''' ..."<br />
<br />
3) Add "/etc/modprobe.d/modprobe.conf" to the FILES section in /etc/mkinitcpio.conf:<br />
FILES="/etc/modprobe.d/modprobe.conf"<br />
<br />
4) Re-generate your initcpio:<br />
# mkinitcpio -p <''your kernel preset (kernel26, etc.)''><br />
<br />
<small>You can also look at the [[Intel Graphics]] instructions for an early start: [[Intel Graphics#KMS_.28Kernel_Mode_Setting.29|Intel Graphics:KMS (Kernel Mode Setting)]]</small><br />
<br />
==== kernel26-nouveau-git ====<br />
With [http://aur.archlinux.org/packages.php?ID=30158 kernel26-nouveau-git], all you need to do is add "nouveau" to HOOKS in /etc/mkinitcpio.conf. For example:<br />
HOOKS="'''nouveau''' base udev autodetect pata scsi sata lvm2 filesystems"<br />
<br />
Then run<br />
# mkinitcpio -p kernel26-nouveau-git<br />
<br />
== Alternative installation ==<br />
<br />
If the official archlinux packages don't work, you could try more current packages from AUR : [http://aur.archlinux.org/packages.php?ID=29602 nouveau-drm-snapshot] and [http://aur.archlinux.org/packages.php?ID=11891 xf86-video-nouveau-git]<br />
<br />
If this still does not work, you can try the way recommended by upstream, which is to install a kernel already including the nouveau drm modules : [http://aur.archlinux.org/packages.php?ID=30158 kernel26-nouveau-git]<br />
<br />
== 3D ==<br />
<br />
Mesa will render some basic things like glxgears in software by default. The nouveau project is developing an accelerated 3D driver, but it is still very experimental and unsupported. Using it to render anything more graphically involved than glxgears is almost guaranteed to crash X, and possibly your whole box. If you want to give it a try anyway, you can install [http://www.archlinux.org/packages/extra/i686/nouveau-dri/ nouveau-dri]. If the nouveau-dri package is too old, you might want to try [http://aur.archlinux.org/packages.php?ID=29024 nouveau-dri-git] from the AUR.<br />
<br />
== DualHead ==<br />
<br />
Nouveau supports the xrandr extension for modesetting and multiple monitors.<br />
<br />
There is a full sample /etc/X11/xorg.conf above for running 2 monitors in dual head mode. You may prefer to use a graphical tool to configure monitors like gnome-display-properties (System -> Preferences -> Display).<br />
<pre><br />
# the right one<br />
Section "Monitor"<br />
Identifier "NEC"<br />
Option "PreferredMode" "1280x1024_60.00"<br />
EndSection<br />
# the left one<br />
Section "Monitor"<br />
Identifier "FUS"<br />
Option "PreferredMode" "1280x1024_60.00"<br />
Option "LeftOf" "NEC"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "nvidia card"<br />
BoardName "nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] rev 161"<br />
Driver "nouveau"<br />
Option "Monitor-DVI-I-0" "NEC"<br />
Option "Monitor-DVI-I-1" "FUS"<br />
#Option "AccelMethod" "XAA"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "screen1"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Virtual 2560 1024<br />
EndSubSection<br />
Device "nvidia card"<br />
EndSection<br />
<br />
Section "ServerLayout"<br />
Identifier "layout1"<br />
Screen "screen1"<br />
# will be replaced by gallium 3D<br />
Option "AIGLX" "false"<br />
EndSection<br />
</pre></div>Cemsbrhttps://wiki.archlinux.org/index.php?title=Dzen&diff=76235Dzen2009-09-20T20:07:06Z<p>Cemsbr: /* Using custom fonts with Dzen */ by ~/.xinitrc</p>
<hr />
<div>[[Category:System Monitor]]<br />
[[Category:HOWTOs (English)]]<br />
[[Category:Eye candy (English)]]<br />
{{Stub}}<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Dzen}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
From the [http://gotmor.googlepages.com/dzen dzen] website:<br />
<br />
''"Dzen is a general purpose messaging, notification and menuing program for X11. It was desigend to be scriptable in any language and integrate well with window managers like dwm, wmii and xmonad though it will work with any windowmanger."''<br />
<br />
=Installation=<br />
dzen is available from the community repository:<br />
# pacman -S dzen2<br />
<br />
<br />
=Tips & Tricks=<br />
<br />
== Using custom fonts with Dzen ==<br />
<br />
If you wish to use custom fonts with dzen2 (like the popular Terminus font), you need to add the path to your local fonts folder in xorg.conf.<br />
<br />
Section "Files"<br />
...<br />
FontPath "/usr/share/fonts/local"<br />
...<br />
EndSection<br />
<br />
If you do not have permission or do not want to change xorg.conf, you may add this to ~/.xinitrc:<br />
<br />
xset +fp /usr/share/fonts/local<br />
xset fp rehash<br />
<br />
== Dzen & conky-cli ==<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=11884&O=0&L=0&C=0&K=conky-cli&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd conky-cli], a stripped-down version of the Conky status utility, can be used to pipe information directly to dzen for output in a statusbar. The following example displays the the loadavg values in red and the current time in the default dzen foreground colour:<br />
<br />
'''~/.conkyrc:'''<br />
background no<br />
out_to_console yes<br />
update_interval 1.0<br />
total_run_times 0<br />
use_spacer none<br />
<br />
TEXT<br />
^fg(#ff0000)${loadavg 1 2 3} ^fg()${time %a %b %d %I:%M%P}<br />
<br />
<br />
'''~/bin/dzconky:'''<br />
<br />
#!/bin/sh<br />
<br />
FG='#aaaaaa'<br />
BG='#1a1a1a'<br />
FONT='-*-terminus-*-r-normal-*-*-120-*-*-*-*-iso8859-*'<br />
conky | dzen2 -e - -h '16' -w '600' -ta r -fg $FG -bg $BG -fn $FONT<br />
<br />
Simply execute ''dzconky'' in your startup scripts.<br />
<br />
== Enabling Xft support for dzen ==<br />
<br />
{{Note|You need to install '''libxft''' package.}}<br />
As of revision 241 (development), dzen2 has optional support for Xft. To enable Xft, you should build dzen2 with these options: ('''edit''' {{filename|config.mk}})<br />
<br />
## Option: With Xinerama and XPM and XFT<br />
LIBS = -L/usr/lib -lc -L${X11LIB} -lX11 -lXinerama -lXpm `pkg-config --libs xft`<br />
CFLAGS = -Wall -Os ${INCS} -DVERSION=\"${VERSION}\" -DDZEN_XINERAMA -DDZEN_XPM -DDZEN_XFT `pkg-config --cflags xft`<br />
<br />
To check libxft support, you can use this command:<br />
<br />
echo "ehlo world" | dzen2 -fn 'Times New Roman' -p</div>Cemsbr