@c  Copyright (C) 2000, 2001, 2002, 2003, 2004  Tom Cato Amundsen
@c  Permission is granted to copy, distribute and/or modify this document
@c  under the terms of the GNU Free Documentation License, Version 1.1
@c  or any later version published by the Free Software Foundation;
@c  with no Invariant Sections.

m4_include(texidefinitions.m4)

@section  Translating Solfege

Solfege can easily be translated to your favourite language. The
translated messages are stored in .po-files, like most GNU programs.


@subsection .po files
Translated messages Solfege give to the user is stored in the @file{po/}
subdir. To add a language, lets say the two letter code is @code{nn},
you do:
@itemize
@item edit @file{po/Makefile}, add the language to the line that look
something like this:
@example
    LANGUAGES=no de @code{nn}
@end example

@item @command{cp solfege-intervalnames.pot solfege-intervalnames-<i>nn</i>.po} and @command{cp solfege.po nn.p}

@item translate the files
@item from srcdir: @code{./configure && make && make install}
@end itemize
 
@subsection .html files
All english html files is stored in @file{online-docs/C/}. Your german
translation should go into @file{online-docs/de/}. Do not translate
the file names.

@subsection Lesson files
Lessonfiles can be translated it two ways. Strings can be marked
to be looked up in the message cataloges (.po-files):
@example
  name = _("Major")
@end example


Or you can include the translation in the lessonfile:
@example
  name = "Major"
  name(no) = "Dur"
  name(fr) = "Majeur"
@end example

Generally, for very common strings, like "major", "minor" etc, you
can use .po-files, but for the rest, you should inlucde the
translation in the lessonfile.

Do @emph{not} mark chord names like @emph{7} or @emph{m7-5} for
translation using .po-files.

