File: FAQ.texi

package info (click to toggle)
solfege 3.23.4-13
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 29,744 kB
  • sloc: python: 26,939; xml: 4,380; ansic: 1,544; sh: 807; makefile: 655; perl: 8; exp: 7
file content (39 lines) | stat: -rw-r--r-- 1,399 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
\input texinfo
@setfilename FAQ.info
@settitle FAQ
@node Top, , , (dir)
@top

@chapter FAQ

See also @url{http://www.solfege.org/Solfege/FrequentlyAskedQuestions}

@section The window title does not display non-ascii characters
... everything look like: "Solfege \x@{0414@}\x@{0438@}\x@{0442@}..."

This is because your window manager does not display unicode fonts.
Try a window manager that can handle unicode fonts, for example metacity.

@section The program crashes at startup!
Try to start the program with the @option{--no-sound}. If the
program starts, then you probably has to check the sound setup
for your kernel. If you for example have a Soundblaster 32 and
unloads the @file{awe_wave} module, Solfege will crash when it tries
to open @file{/dev/music}.

@section ValueError: invalid literal for float():
If you want translated messages, you should only set the @env{LC_MESSAGES}
environment variable, not @env{LC_ALL} or @env{LC_NUMERIC}. If your
window manager set these variable, you can avoid the problem by running
solfege like this:

@command{LC_NUMERIC=C solfege}

You can run the @command{locale} command to see what environment
variables controlling locales are set.

@section Some menu entries are blank when I use language other than english.
If you are running Debian with glibc > 2.2, try to rerun
@command{locale-gen} as root, and maybe edit @file{/etc/locale.gen}.

@bye