[musicians-guide/f14] refresh POT and PO files
Rüdiger Landmann
rlandmann at fedoraproject.org
Tue Nov 2 04:51:34 UTC 2010
commit bbb64d239faeadd780487fff3270c05e4bddb3ab
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Tue Nov 2 14:52:17 2010 +1000
refresh POT and PO files
as-IN/Ardour.po | 209 +++++++++++++------
as-IN/Audacity.po | 87 +++++++-
as-IN/Audio_Vocabulary.po | 63 ++++++-
as-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
as-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
as-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
as-IN/LilyPond/LilyPond-piano.po | 22 +-
as-IN/LilyPond/LilyPond-syntax.po | 12 +-
as-IN/Planet_CCRMA_at_Home.po | 13 +-
as-IN/Qtractor.po | 28 ++--
as-IN/Revision_History.po | 12 +-
as-IN/Rosegarden.po | 24 +-
as-IN/Solfege.po | 6 +-
as-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
as-IN/SuperCollider/SuperCollider.po | 8 +-
bn-IN/Ardour.po | 209 +++++++++++++------
bn-IN/Audacity.po | 87 +++++++-
bn-IN/Audio_Vocabulary.po | 63 ++++++-
bn-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
bn-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
bn-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
bn-IN/LilyPond/LilyPond-piano.po | 22 +-
bn-IN/LilyPond/LilyPond-syntax.po | 12 +-
bn-IN/Planet_CCRMA_at_Home.po | 13 +-
bn-IN/Qtractor.po | 28 ++--
bn-IN/Revision_History.po | 12 +-
bn-IN/Rosegarden.po | 24 +-
bn-IN/Solfege.po | 6 +-
bn-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
bn-IN/SuperCollider/SuperCollider.po | 8 +-
cs-CZ/Ardour.po | 209 +++++++++++++------
cs-CZ/Audacity.po | 87 +++++++-
cs-CZ/Audio_Vocabulary.po | 63 ++++++-
cs-CZ/Digital_Audio_Workstations.po | 152 ++++++++++++--
cs-CZ/LilyPond/LilyPond-counterpoint.po | 10 +-
cs-CZ/LilyPond/LilyPond-orchestra.po | 36 ++--
cs-CZ/LilyPond/LilyPond-piano.po | 22 +-
cs-CZ/LilyPond/LilyPond-syntax.po | 12 +-
cs-CZ/Planet_CCRMA_at_Home.po | 13 +-
cs-CZ/Qtractor.po | 28 ++--
cs-CZ/Revision_History.po | 12 +-
cs-CZ/Rosegarden.po | 24 +-
cs-CZ/Solfege.po | 6 +-
cs-CZ/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
cs-CZ/SuperCollider/SuperCollider.po | 8 +-
de-DE/Ardour.po | 209 +++++++++++++------
de-DE/Audacity.po | 87 +++++++-
de-DE/Audio_Vocabulary.po | 63 ++++++-
de-DE/Digital_Audio_Workstations.po | 152 ++++++++++++--
de-DE/LilyPond/LilyPond-counterpoint.po | 10 +-
de-DE/LilyPond/LilyPond-orchestra.po | 36 ++--
de-DE/LilyPond/LilyPond-piano.po | 22 +-
de-DE/LilyPond/LilyPond-syntax.po | 12 +-
de-DE/Planet_CCRMA_at_Home.po | 13 +-
de-DE/Qtractor.po | 28 ++--
de-DE/Revision_History.po | 12 +-
de-DE/Rosegarden.po | 24 +-
de-DE/Solfege.po | 6 +-
de-DE/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
de-DE/SuperCollider/SuperCollider.po | 8 +-
el-GR/Ardour.po | 209 +++++++++++++------
el-GR/Audacity.po | 87 +++++++-
el-GR/Audio_Vocabulary.po | 63 ++++++-
el-GR/Digital_Audio_Workstations.po | 152 ++++++++++++--
el-GR/LilyPond/LilyPond-counterpoint.po | 10 +-
el-GR/LilyPond/LilyPond-orchestra.po | 36 ++--
el-GR/LilyPond/LilyPond-piano.po | 22 +-
el-GR/LilyPond/LilyPond-syntax.po | 12 +-
el-GR/Planet_CCRMA_at_Home.po | 13 +-
el-GR/Qtractor.po | 28 ++--
el-GR/Revision_History.po | 12 +-
el-GR/Rosegarden.po | 24 +-
el-GR/Solfege.po | 6 +-
el-GR/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
el-GR/SuperCollider/SuperCollider.po | 8 +-
en-US/Musicians_Guide.xml | 2 +-
es-ES/Ardour.po | 209 +++++++++++++------
es-ES/Audacity.po | 87 +++++++-
es-ES/Audio_Vocabulary.po | 63 ++++++-
es-ES/Digital_Audio_Workstations.po | 152 ++++++++++++--
es-ES/LilyPond/LilyPond-counterpoint.po | 10 +-
es-ES/LilyPond/LilyPond-orchestra.po | 36 ++--
es-ES/LilyPond/LilyPond-piano.po | 22 +-
es-ES/LilyPond/LilyPond-syntax.po | 12 +-
es-ES/Planet_CCRMA_at_Home.po | 13 +-
es-ES/Qtractor.po | 28 ++--
es-ES/Revision_History.po | 12 +-
es-ES/Rosegarden.po | 24 +-
es-ES/Solfege.po | 6 +-
es-ES/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
es-ES/SuperCollider/SuperCollider.po | 8 +-
fr-FR/Ardour.po | 209 +++++++++++++------
fr-FR/Audacity.po | 87 +++++++-
fr-FR/Audio_Vocabulary.po | 63 ++++++-
fr-FR/Digital_Audio_Workstations.po | 152 ++++++++++++--
fr-FR/LilyPond/LilyPond-counterpoint.po | 10 +-
fr-FR/LilyPond/LilyPond-orchestra.po | 36 ++--
fr-FR/LilyPond/LilyPond-piano.po | 22 +-
fr-FR/LilyPond/LilyPond-syntax.po | 12 +-
fr-FR/Planet_CCRMA_at_Home.po | 13 +-
fr-FR/Qtractor.po | 28 ++--
fr-FR/Revision_History.po | 12 +-
fr-FR/Rosegarden.po | 24 +-
fr-FR/Solfege.po | 6 +-
fr-FR/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
fr-FR/SuperCollider/SuperCollider.po | 8 +-
gu-IN/Ardour.po | 209 +++++++++++++------
gu-IN/Audacity.po | 87 +++++++-
gu-IN/Audio_Vocabulary.po | 63 ++++++-
gu-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
gu-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
gu-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
gu-IN/LilyPond/LilyPond-piano.po | 22 +-
gu-IN/LilyPond/LilyPond-syntax.po | 12 +-
gu-IN/Planet_CCRMA_at_Home.po | 13 +-
gu-IN/Qtractor.po | 28 ++--
gu-IN/Revision_History.po | 12 +-
gu-IN/Rosegarden.po | 24 +-
gu-IN/Solfege.po | 6 +-
gu-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
gu-IN/SuperCollider/SuperCollider.po | 8 +-
hi-IN/Ardour.po | 209 +++++++++++++------
hi-IN/Audacity.po | 87 +++++++-
hi-IN/Audio_Vocabulary.po | 63 ++++++-
hi-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
hi-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
hi-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
hi-IN/LilyPond/LilyPond-piano.po | 22 +-
hi-IN/LilyPond/LilyPond-syntax.po | 12 +-
hi-IN/Planet_CCRMA_at_Home.po | 13 +-
hi-IN/Qtractor.po | 28 ++--
hi-IN/Revision_History.po | 12 +-
hi-IN/Rosegarden.po | 24 +-
hi-IN/Solfege.po | 6 +-
hi-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
hi-IN/SuperCollider/SuperCollider.po | 8 +-
id-ID/Ardour.po | 209 +++++++++++++------
id-ID/Audacity.po | 87 +++++++-
id-ID/Audio_Vocabulary.po | 63 ++++++-
id-ID/Digital_Audio_Workstations.po | 152 ++++++++++++--
id-ID/LilyPond/LilyPond-counterpoint.po | 10 +-
id-ID/LilyPond/LilyPond-orchestra.po | 36 ++--
id-ID/LilyPond/LilyPond-piano.po | 22 +-
id-ID/LilyPond/LilyPond-syntax.po | 12 +-
id-ID/Planet_CCRMA_at_Home.po | 13 +-
id-ID/Qtractor.po | 28 ++--
id-ID/Revision_History.po | 12 +-
id-ID/Rosegarden.po | 24 +-
id-ID/Solfege.po | 6 +-
id-ID/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
id-ID/SuperCollider/SuperCollider.po | 8 +-
it-IT/Ardour.po | 209 +++++++++++++------
it-IT/Audacity.po | 87 +++++++-
it-IT/Audio_Vocabulary.po | 63 ++++++-
it-IT/Digital_Audio_Workstations.po | 152 ++++++++++++--
it-IT/LilyPond/LilyPond-counterpoint.po | 10 +-
it-IT/LilyPond/LilyPond-orchestra.po | 36 ++--
it-IT/LilyPond/LilyPond-piano.po | 22 +-
it-IT/LilyPond/LilyPond-syntax.po | 12 +-
it-IT/Planet_CCRMA_at_Home.po | 13 +-
it-IT/Qtractor.po | 28 ++--
it-IT/Revision_History.po | 12 +-
it-IT/Rosegarden.po | 24 +-
it-IT/Solfege.po | 6 +-
it-IT/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
it-IT/SuperCollider/SuperCollider.po | 8 +-
ja-JP/Ardour.po | 209 +++++++++++++------
ja-JP/Audacity.po | 87 +++++++-
ja-JP/Audio_Vocabulary.po | 63 ++++++-
ja-JP/Digital_Audio_Workstations.po | 152 ++++++++++++--
ja-JP/LilyPond/LilyPond-counterpoint.po | 10 +-
ja-JP/LilyPond/LilyPond-orchestra.po | 36 ++--
ja-JP/LilyPond/LilyPond-piano.po | 22 +-
ja-JP/LilyPond/LilyPond-syntax.po | 12 +-
ja-JP/Planet_CCRMA_at_Home.po | 13 +-
ja-JP/Qtractor.po | 28 ++--
ja-JP/Revision_History.po | 12 +-
ja-JP/Rosegarden.po | 24 +-
ja-JP/Solfege.po | 6 +-
ja-JP/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
ja-JP/SuperCollider/SuperCollider.po | 8 +-
kn-IN/Ardour.po | 209 +++++++++++++------
kn-IN/Audacity.po | 87 +++++++-
kn-IN/Audio_Vocabulary.po | 63 ++++++-
kn-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
kn-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
kn-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
kn-IN/LilyPond/LilyPond-piano.po | 22 +-
kn-IN/LilyPond/LilyPond-syntax.po | 12 +-
kn-IN/Planet_CCRMA_at_Home.po | 13 +-
kn-IN/Qtractor.po | 28 ++--
kn-IN/Revision_History.po | 12 +-
kn-IN/Rosegarden.po | 24 +-
kn-IN/Solfege.po | 6 +-
kn-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
kn-IN/SuperCollider/SuperCollider.po | 8 +-
ml-IN/Ardour.po | 209 +++++++++++++------
ml-IN/Audacity.po | 87 +++++++-
ml-IN/Audio_Vocabulary.po | 63 ++++++-
ml-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
ml-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
ml-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
ml-IN/LilyPond/LilyPond-piano.po | 22 +-
ml-IN/LilyPond/LilyPond-syntax.po | 12 +-
ml-IN/Planet_CCRMA_at_Home.po | 13 +-
ml-IN/Qtractor.po | 28 ++--
ml-IN/Revision_History.po | 12 +-
ml-IN/Rosegarden.po | 24 +-
ml-IN/Solfege.po | 6 +-
ml-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
ml-IN/SuperCollider/SuperCollider.po | 8 +-
mr-IN/Ardour.po | 209 +++++++++++++------
mr-IN/Audacity.po | 87 +++++++-
mr-IN/Audio_Vocabulary.po | 63 ++++++-
mr-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
mr-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
mr-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
mr-IN/LilyPond/LilyPond-piano.po | 22 +-
mr-IN/LilyPond/LilyPond-syntax.po | 12 +-
mr-IN/Planet_CCRMA_at_Home.po | 13 +-
mr-IN/Qtractor.po | 28 ++--
mr-IN/Revision_History.po | 12 +-
mr-IN/Rosegarden.po | 24 +-
mr-IN/Solfege.po | 6 +-
mr-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
mr-IN/SuperCollider/SuperCollider.po | 8 +-
nl-NL/Ardour.po | 209 +++++++++++++------
nl-NL/Audacity.po | 87 +++++++-
nl-NL/Audio_Vocabulary.po | 63 ++++++-
nl-NL/Digital_Audio_Workstations.po | 152 ++++++++++++--
nl-NL/LilyPond/LilyPond-counterpoint.po | 10 +-
nl-NL/LilyPond/LilyPond-orchestra.po | 36 ++--
nl-NL/LilyPond/LilyPond-piano.po | 22 +-
nl-NL/LilyPond/LilyPond-syntax.po | 12 +-
nl-NL/Planet_CCRMA_at_Home.po | 13 +-
nl-NL/Qtractor.po | 28 ++--
nl-NL/Revision_History.po | 12 +-
nl-NL/Rosegarden.po | 24 +-
nl-NL/Solfege.po | 6 +-
nl-NL/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
nl-NL/SuperCollider/SuperCollider.po | 8 +-
or-IN/Ardour.po | 209 +++++++++++++------
or-IN/Audacity.po | 87 +++++++-
or-IN/Audio_Vocabulary.po | 63 ++++++-
or-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
or-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
or-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
or-IN/LilyPond/LilyPond-piano.po | 22 +-
or-IN/LilyPond/LilyPond-syntax.po | 12 +-
or-IN/Planet_CCRMA_at_Home.po | 13 +-
or-IN/Qtractor.po | 28 ++--
or-IN/Revision_History.po | 12 +-
or-IN/Rosegarden.po | 24 +-
or-IN/Solfege.po | 6 +-
or-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
or-IN/SuperCollider/SuperCollider.po | 8 +-
pa-IN/Ardour.po | 209 +++++++++++++------
pa-IN/Audacity.po | 87 +++++++-
pa-IN/Audio_Vocabulary.po | 63 ++++++-
pa-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
pa-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
pa-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
pa-IN/LilyPond/LilyPond-piano.po | 22 +-
pa-IN/LilyPond/LilyPond-syntax.po | 12 +-
pa-IN/Planet_CCRMA_at_Home.po | 13 +-
pa-IN/Qtractor.po | 28 ++--
pa-IN/Revision_History.po | 12 +-
pa-IN/Rosegarden.po | 24 +-
pa-IN/Solfege.po | 6 +-
pa-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
pa-IN/SuperCollider/SuperCollider.po | 8 +-
pl-PL/Ardour.po | 209 +++++++++++++------
pl-PL/Audacity.po | 87 +++++++-
pl-PL/Audio_Vocabulary.po | 63 ++++++-
pl-PL/Digital_Audio_Workstations.po | 152 ++++++++++++--
pl-PL/LilyPond/LilyPond-counterpoint.po | 10 +-
pl-PL/LilyPond/LilyPond-orchestra.po | 36 ++--
pl-PL/LilyPond/LilyPond-piano.po | 22 +-
pl-PL/LilyPond/LilyPond-syntax.po | 12 +-
pl-PL/Planet_CCRMA_at_Home.po | 13 +-
pl-PL/Qtractor.po | 28 ++--
pl-PL/Revision_History.po | 12 +-
pl-PL/Rosegarden.po | 24 +-
pl-PL/Solfege.po | 6 +-
pl-PL/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
pl-PL/SuperCollider/SuperCollider.po | 8 +-
pot/Ardour.pot | 211 +++++++++++++-------
pot/Audacity.pot | 88 +++++++--
pot/Audio_Vocabulary.pot | 65 ++++++-
pot/Author_Group.pot | 4 +-
pot/Book_Info.pot | 4 +-
pot/Chapter.pot | 4 +-
pot/Digital_Audio_Workstations.pot | 154 ++++++++++++--
pot/FluidSynth.pot | 4 +-
pot/Frescobaldi.pot | 4 +-
pot/LilyPond/LilyPond-counterpoint.pot | 12 +-
pot/LilyPond/LilyPond-orchestra.pot | 38 ++--
pot/LilyPond/LilyPond-piano.pot | 24 +-
pot/LilyPond/LilyPond-syntax.pot | 14 +-
pot/LilyPond/LilyPond.pot | 4 +-
pot/Musicians_Guide.pot | 4 +-
pot/Planet_CCRMA_at_Home.pot | 14 +-
pot/Preface.pot | 4 +-
pot/Qtractor.pot | 30 ++--
pot/Real_Time_and_Low_Latency.pot | 4 +-
pot/Revision_History.pot | 14 +-
pot/Rosegarden.pot | 26 ++--
pot/Solfege.pot | 8 +-
pot/Sound_Cards.pot | 26 ++-
pot/Sound_Servers.pot | 4 +-
.../SuperCollider-Basic_Programming.pot | 32 ++--
pot/SuperCollider/SuperCollider-Composing.pot | 4 +-
pot/SuperCollider/SuperCollider-Exporting.pot | 4 +-
pot/SuperCollider/SuperCollider.pot | 10 +-
pt-BR/Ardour.po | 209 +++++++++++++------
pt-BR/Audacity.po | 87 +++++++-
pt-BR/Audio_Vocabulary.po | 63 ++++++-
pt-BR/Digital_Audio_Workstations.po | 152 ++++++++++++--
pt-BR/LilyPond/LilyPond-counterpoint.po | 10 +-
pt-BR/LilyPond/LilyPond-orchestra.po | 36 ++--
pt-BR/LilyPond/LilyPond-piano.po | 22 +-
pt-BR/LilyPond/LilyPond-syntax.po | 12 +-
pt-BR/Planet_CCRMA_at_Home.po | 13 +-
pt-BR/Qtractor.po | 28 ++--
pt-BR/Revision_History.po | 12 +-
pt-BR/Rosegarden.po | 24 +-
pt-BR/Solfege.po | 6 +-
pt-BR/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
pt-BR/SuperCollider/SuperCollider.po | 8 +-
pt-PT/Ardour.po | 209 +++++++++++++------
pt-PT/Audacity.po | 87 +++++++-
pt-PT/Audio_Vocabulary.po | 63 ++++++-
pt-PT/Digital_Audio_Workstations.po | 152 ++++++++++++--
pt-PT/LilyPond/LilyPond-counterpoint.po | 10 +-
pt-PT/LilyPond/LilyPond-orchestra.po | 36 ++--
pt-PT/LilyPond/LilyPond-piano.po | 22 +-
pt-PT/LilyPond/LilyPond-syntax.po | 12 +-
pt-PT/Planet_CCRMA_at_Home.po | 13 +-
pt-PT/Qtractor.po | 28 ++--
pt-PT/Revision_History.po | 12 +-
pt-PT/Rosegarden.po | 24 +-
pt-PT/Solfege.po | 6 +-
pt-PT/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
pt-PT/SuperCollider/SuperCollider.po | 8 +-
publican.cfg | 3 -
ru-RU/Ardour.po | 209 +++++++++++++------
ru-RU/Audacity.po | 87 +++++++-
ru-RU/Audio_Vocabulary.po | 63 ++++++-
ru-RU/Digital_Audio_Workstations.po | 152 ++++++++++++--
ru-RU/LilyPond/LilyPond-counterpoint.po | 10 +-
ru-RU/LilyPond/LilyPond-orchestra.po | 36 ++--
ru-RU/LilyPond/LilyPond-piano.po | 22 +-
ru-RU/LilyPond/LilyPond-syntax.po | 12 +-
ru-RU/Planet_CCRMA_at_Home.po | 13 +-
ru-RU/Qtractor.po | 28 ++--
ru-RU/Revision_History.po | 12 +-
ru-RU/Rosegarden.po | 24 +-
ru-RU/Solfege.po | 6 +-
ru-RU/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
ru-RU/SuperCollider/SuperCollider.po | 8 +-
sr-Latn-RS/Ardour.po | 209 +++++++++++++------
sr-Latn-RS/Audacity.po | 87 +++++++-
sr-Latn-RS/Audio_Vocabulary.po | 63 ++++++-
sr-Latn-RS/Digital_Audio_Workstations.po | 152 ++++++++++++--
sr-Latn-RS/LilyPond/LilyPond-counterpoint.po | 10 +-
sr-Latn-RS/LilyPond/LilyPond-orchestra.po | 36 ++--
sr-Latn-RS/LilyPond/LilyPond-piano.po | 22 +-
sr-Latn-RS/LilyPond/LilyPond-syntax.po | 12 +-
sr-Latn-RS/Planet_CCRMA_at_Home.po | 13 +-
sr-Latn-RS/Qtractor.po | 28 ++--
sr-Latn-RS/Revision_History.po | 12 +-
sr-Latn-RS/Rosegarden.po | 24 +-
sr-Latn-RS/Solfege.po | 6 +-
sr-Latn-RS/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
sr-Latn-RS/SuperCollider/SuperCollider.po | 8 +-
sr-RS/Ardour.po | 209 +++++++++++++------
sr-RS/Audacity.po | 87 +++++++-
sr-RS/Audio_Vocabulary.po | 63 ++++++-
sr-RS/Digital_Audio_Workstations.po | 152 ++++++++++++--
sr-RS/LilyPond/LilyPond-counterpoint.po | 10 +-
sr-RS/LilyPond/LilyPond-orchestra.po | 36 ++--
sr-RS/LilyPond/LilyPond-piano.po | 22 +-
sr-RS/LilyPond/LilyPond-syntax.po | 12 +-
sr-RS/Planet_CCRMA_at_Home.po | 13 +-
sr-RS/Qtractor.po | 28 ++--
sr-RS/Revision_History.po | 12 +-
sr-RS/Rosegarden.po | 24 +-
sr-RS/Solfege.po | 6 +-
sr-RS/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
sr-RS/SuperCollider/SuperCollider.po | 8 +-
sv-SE/Ardour.po | 209 +++++++++++++------
sv-SE/Audacity.po | 87 +++++++-
sv-SE/Audio_Vocabulary.po | 63 ++++++-
sv-SE/Digital_Audio_Workstations.po | 152 ++++++++++++--
sv-SE/LilyPond/LilyPond-counterpoint.po | 10 +-
sv-SE/LilyPond/LilyPond-orchestra.po | 36 ++--
sv-SE/LilyPond/LilyPond-piano.po | 22 +-
sv-SE/LilyPond/LilyPond-syntax.po | 12 +-
sv-SE/Planet_CCRMA_at_Home.po | 13 +-
sv-SE/Qtractor.po | 28 ++--
sv-SE/Revision_History.po | 12 +-
sv-SE/Rosegarden.po | 24 +-
sv-SE/Solfege.po | 6 +-
sv-SE/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
sv-SE/SuperCollider/SuperCollider.po | 8 +-
ta-IN/Ardour.po | 209 +++++++++++++------
ta-IN/Audacity.po | 87 +++++++-
ta-IN/Audio_Vocabulary.po | 63 ++++++-
ta-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
ta-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
ta-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
ta-IN/LilyPond/LilyPond-piano.po | 22 +-
ta-IN/LilyPond/LilyPond-syntax.po | 12 +-
ta-IN/Planet_CCRMA_at_Home.po | 13 +-
ta-IN/Qtractor.po | 28 ++--
ta-IN/Revision_History.po | 12 +-
ta-IN/Rosegarden.po | 24 +-
ta-IN/Solfege.po | 6 +-
ta-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
ta-IN/SuperCollider/SuperCollider.po | 8 +-
te-IN/Ardour.po | 209 +++++++++++++------
te-IN/Audacity.po | 87 +++++++-
te-IN/Audio_Vocabulary.po | 63 ++++++-
te-IN/Digital_Audio_Workstations.po | 152 ++++++++++++--
te-IN/LilyPond/LilyPond-counterpoint.po | 10 +-
te-IN/LilyPond/LilyPond-orchestra.po | 36 ++--
te-IN/LilyPond/LilyPond-piano.po | 22 +-
te-IN/LilyPond/LilyPond-syntax.po | 12 +-
te-IN/Planet_CCRMA_at_Home.po | 13 +-
te-IN/Qtractor.po | 28 ++--
te-IN/Revision_History.po | 12 +-
te-IN/Rosegarden.po | 24 +-
te-IN/Solfege.po | 6 +-
te-IN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
te-IN/SuperCollider/SuperCollider.po | 8 +-
uk-UA/Ardour.po | 209 +++++++++++++------
uk-UA/Audacity.po | 87 +++++++-
uk-UA/Audio_Vocabulary.po | 63 ++++++-
uk-UA/Digital_Audio_Workstations.po | 152 ++++++++++++--
uk-UA/LilyPond/LilyPond-counterpoint.po | 10 +-
uk-UA/LilyPond/LilyPond-orchestra.po | 36 ++--
uk-UA/LilyPond/LilyPond-piano.po | 22 +-
uk-UA/LilyPond/LilyPond-syntax.po | 12 +-
uk-UA/Planet_CCRMA_at_Home.po | 13 +-
uk-UA/Qtractor.po | 28 ++--
uk-UA/Revision_History.po | 12 +-
uk-UA/Rosegarden.po | 24 +-
uk-UA/Solfege.po | 6 +-
uk-UA/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
uk-UA/SuperCollider/SuperCollider.po | 8 +-
zh-CN/Ardour.po | 209 +++++++++++++------
zh-CN/Audacity.po | 87 +++++++-
zh-CN/Audio_Vocabulary.po | 95 +++++++--
zh-CN/Book_Info.po | 16 +-
zh-CN/Digital_Audio_Workstations.po | 152 ++++++++++++--
zh-CN/LilyPond/LilyPond-counterpoint.po | 10 +-
zh-CN/LilyPond/LilyPond-orchestra.po | 36 ++--
zh-CN/LilyPond/LilyPond-piano.po | 22 +-
zh-CN/LilyPond/LilyPond-syntax.po | 12 +-
zh-CN/Musicians_Guide.po | 16 +-
zh-CN/Planet_CCRMA_at_Home.po | 13 +-
zh-CN/Qtractor.po | 28 ++--
zh-CN/Revision_History.po | 12 +-
zh-CN/Rosegarden.po | 24 +-
zh-CN/Solfege.po | 6 +-
zh-CN/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
zh-CN/SuperCollider/SuperCollider.po | 8 +-
zh-TW/Ardour.po | 209 +++++++++++++------
zh-TW/Audacity.po | 87 +++++++-
zh-TW/Audio_Vocabulary.po | 63 ++++++-
zh-TW/Digital_Audio_Workstations.po | 152 ++++++++++++--
zh-TW/LilyPond/LilyPond-counterpoint.po | 10 +-
zh-TW/LilyPond/LilyPond-orchestra.po | 36 ++--
zh-TW/LilyPond/LilyPond-piano.po | 22 +-
zh-TW/LilyPond/LilyPond-syntax.po | 12 +-
zh-TW/Planet_CCRMA_at_Home.po | 13 +-
zh-TW/Qtractor.po | 28 ++--
zh-TW/Revision_History.po | 12 +-
zh-TW/Rosegarden.po | 24 +-
zh-TW/Solfege.po | 6 +-
zh-TW/Sound_Cards.po | 24 ++-
.../SuperCollider-Basic_Programming.po | 30 ++--
zh-TW/SuperCollider/SuperCollider.po | 8 +-
512 files changed, 16594 insertions(+), 6369 deletions(-)
---
diff --git a/as-IN/Ardour.po b/as-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/as-IN/Ardour.po
+++ b/as-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/as-IN/Audacity.po b/as-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/as-IN/Audacity.po
+++ b/as-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/as-IN/Audio_Vocabulary.po b/as-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/as-IN/Audio_Vocabulary.po
+++ b/as-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/as-IN/Digital_Audio_Workstations.po b/as-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/as-IN/Digital_Audio_Workstations.po
+++ b/as-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/as-IN/LilyPond/LilyPond-counterpoint.po b/as-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/as-IN/LilyPond/LilyPond-counterpoint.po
+++ b/as-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/as-IN/LilyPond/LilyPond-orchestra.po b/as-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/as-IN/LilyPond/LilyPond-orchestra.po
+++ b/as-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/as-IN/LilyPond/LilyPond-piano.po b/as-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/as-IN/LilyPond/LilyPond-piano.po
+++ b/as-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/as-IN/LilyPond/LilyPond-syntax.po b/as-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/as-IN/LilyPond/LilyPond-syntax.po
+++ b/as-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/as-IN/Planet_CCRMA_at_Home.po b/as-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/as-IN/Planet_CCRMA_at_Home.po
+++ b/as-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/as-IN/Qtractor.po b/as-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/as-IN/Qtractor.po
+++ b/as-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/as-IN/Revision_History.po b/as-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/as-IN/Revision_History.po
+++ b/as-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/as-IN/Rosegarden.po b/as-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/as-IN/Rosegarden.po
+++ b/as-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/as-IN/Solfege.po b/as-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/as-IN/Solfege.po
+++ b/as-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/as-IN/Sound_Cards.po b/as-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/as-IN/Sound_Cards.po
+++ b/as-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/as-IN/SuperCollider/SuperCollider-Basic_Programming.po b/as-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/as-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/as-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/as-IN/SuperCollider/SuperCollider.po b/as-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/as-IN/SuperCollider/SuperCollider.po
+++ b/as-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/bn-IN/Ardour.po b/bn-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/bn-IN/Ardour.po
+++ b/bn-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/bn-IN/Audacity.po b/bn-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/bn-IN/Audacity.po
+++ b/bn-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/bn-IN/Audio_Vocabulary.po b/bn-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/bn-IN/Audio_Vocabulary.po
+++ b/bn-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/bn-IN/Digital_Audio_Workstations.po b/bn-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/bn-IN/Digital_Audio_Workstations.po
+++ b/bn-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/bn-IN/LilyPond/LilyPond-counterpoint.po b/bn-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/bn-IN/LilyPond/LilyPond-counterpoint.po
+++ b/bn-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/bn-IN/LilyPond/LilyPond-orchestra.po b/bn-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/bn-IN/LilyPond/LilyPond-orchestra.po
+++ b/bn-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/bn-IN/LilyPond/LilyPond-piano.po b/bn-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/bn-IN/LilyPond/LilyPond-piano.po
+++ b/bn-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/bn-IN/LilyPond/LilyPond-syntax.po b/bn-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/bn-IN/LilyPond/LilyPond-syntax.po
+++ b/bn-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/bn-IN/Planet_CCRMA_at_Home.po b/bn-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/bn-IN/Planet_CCRMA_at_Home.po
+++ b/bn-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/bn-IN/Qtractor.po b/bn-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/bn-IN/Qtractor.po
+++ b/bn-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/bn-IN/Revision_History.po b/bn-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/bn-IN/Revision_History.po
+++ b/bn-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/bn-IN/Rosegarden.po b/bn-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/bn-IN/Rosegarden.po
+++ b/bn-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/bn-IN/Solfege.po b/bn-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/bn-IN/Solfege.po
+++ b/bn-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/bn-IN/Sound_Cards.po b/bn-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/bn-IN/Sound_Cards.po
+++ b/bn-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/bn-IN/SuperCollider/SuperCollider-Basic_Programming.po b/bn-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/bn-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/bn-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/bn-IN/SuperCollider/SuperCollider.po b/bn-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/bn-IN/SuperCollider/SuperCollider.po
+++ b/bn-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Ardour.po b/cs-CZ/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/cs-CZ/Ardour.po
+++ b/cs-CZ/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/cs-CZ/Audacity.po b/cs-CZ/Audacity.po
index cb97802..0e4ae65 100644
--- a/cs-CZ/Audacity.po
+++ b/cs-CZ/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Audio_Vocabulary.po b/cs-CZ/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/cs-CZ/Audio_Vocabulary.po
+++ b/cs-CZ/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Digital_Audio_Workstations.po b/cs-CZ/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/cs-CZ/Digital_Audio_Workstations.po
+++ b/cs-CZ/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/cs-CZ/LilyPond/LilyPond-counterpoint.po b/cs-CZ/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/cs-CZ/LilyPond/LilyPond-counterpoint.po
+++ b/cs-CZ/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/LilyPond/LilyPond-orchestra.po b/cs-CZ/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/cs-CZ/LilyPond/LilyPond-orchestra.po
+++ b/cs-CZ/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/LilyPond/LilyPond-piano.po b/cs-CZ/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/cs-CZ/LilyPond/LilyPond-piano.po
+++ b/cs-CZ/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/LilyPond/LilyPond-syntax.po b/cs-CZ/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/cs-CZ/LilyPond/LilyPond-syntax.po
+++ b/cs-CZ/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/cs-CZ/Planet_CCRMA_at_Home.po b/cs-CZ/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/cs-CZ/Planet_CCRMA_at_Home.po
+++ b/cs-CZ/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Qtractor.po b/cs-CZ/Qtractor.po
index fdaa731..0a2210e 100644
--- a/cs-CZ/Qtractor.po
+++ b/cs-CZ/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Revision_History.po b/cs-CZ/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/cs-CZ/Revision_History.po
+++ b/cs-CZ/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/cs-CZ/Rosegarden.po b/cs-CZ/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/cs-CZ/Rosegarden.po
+++ b/cs-CZ/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Solfege.po b/cs-CZ/Solfege.po
index 673c88c..8110ddb 100644
--- a/cs-CZ/Solfege.po
+++ b/cs-CZ/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/Sound_Cards.po b/cs-CZ/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/cs-CZ/Sound_Cards.po
+++ b/cs-CZ/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/cs-CZ/SuperCollider/SuperCollider-Basic_Programming.po b/cs-CZ/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/cs-CZ/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/cs-CZ/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/cs-CZ/SuperCollider/SuperCollider.po b/cs-CZ/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/cs-CZ/SuperCollider/SuperCollider.po
+++ b/cs-CZ/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/de-DE/Ardour.po b/de-DE/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/de-DE/Ardour.po
+++ b/de-DE/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/de-DE/Audacity.po b/de-DE/Audacity.po
index cb97802..0e4ae65 100644
--- a/de-DE/Audacity.po
+++ b/de-DE/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/de-DE/Audio_Vocabulary.po b/de-DE/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/de-DE/Audio_Vocabulary.po
+++ b/de-DE/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/de-DE/Digital_Audio_Workstations.po b/de-DE/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/de-DE/Digital_Audio_Workstations.po
+++ b/de-DE/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/de-DE/LilyPond/LilyPond-counterpoint.po b/de-DE/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/de-DE/LilyPond/LilyPond-counterpoint.po
+++ b/de-DE/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/de-DE/LilyPond/LilyPond-orchestra.po b/de-DE/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/de-DE/LilyPond/LilyPond-orchestra.po
+++ b/de-DE/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/de-DE/LilyPond/LilyPond-piano.po b/de-DE/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/de-DE/LilyPond/LilyPond-piano.po
+++ b/de-DE/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/de-DE/LilyPond/LilyPond-syntax.po b/de-DE/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/de-DE/LilyPond/LilyPond-syntax.po
+++ b/de-DE/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/de-DE/Planet_CCRMA_at_Home.po b/de-DE/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/de-DE/Planet_CCRMA_at_Home.po
+++ b/de-DE/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/de-DE/Qtractor.po b/de-DE/Qtractor.po
index fdaa731..0a2210e 100644
--- a/de-DE/Qtractor.po
+++ b/de-DE/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/de-DE/Revision_History.po b/de-DE/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/de-DE/Revision_History.po
+++ b/de-DE/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/de-DE/Rosegarden.po b/de-DE/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/de-DE/Rosegarden.po
+++ b/de-DE/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/de-DE/Solfege.po b/de-DE/Solfege.po
index 673c88c..8110ddb 100644
--- a/de-DE/Solfege.po
+++ b/de-DE/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/de-DE/Sound_Cards.po b/de-DE/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/de-DE/Sound_Cards.po
+++ b/de-DE/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/de-DE/SuperCollider/SuperCollider-Basic_Programming.po b/de-DE/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/de-DE/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/de-DE/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/de-DE/SuperCollider/SuperCollider.po b/de-DE/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/de-DE/SuperCollider/SuperCollider.po
+++ b/de-DE/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/el-GR/Ardour.po b/el-GR/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/el-GR/Ardour.po
+++ b/el-GR/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/el-GR/Audacity.po b/el-GR/Audacity.po
index cb97802..0e4ae65 100644
--- a/el-GR/Audacity.po
+++ b/el-GR/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/el-GR/Audio_Vocabulary.po b/el-GR/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/el-GR/Audio_Vocabulary.po
+++ b/el-GR/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/el-GR/Digital_Audio_Workstations.po b/el-GR/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/el-GR/Digital_Audio_Workstations.po
+++ b/el-GR/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/el-GR/LilyPond/LilyPond-counterpoint.po b/el-GR/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/el-GR/LilyPond/LilyPond-counterpoint.po
+++ b/el-GR/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/el-GR/LilyPond/LilyPond-orchestra.po b/el-GR/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/el-GR/LilyPond/LilyPond-orchestra.po
+++ b/el-GR/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/el-GR/LilyPond/LilyPond-piano.po b/el-GR/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/el-GR/LilyPond/LilyPond-piano.po
+++ b/el-GR/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/el-GR/LilyPond/LilyPond-syntax.po b/el-GR/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/el-GR/LilyPond/LilyPond-syntax.po
+++ b/el-GR/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/el-GR/Planet_CCRMA_at_Home.po b/el-GR/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/el-GR/Planet_CCRMA_at_Home.po
+++ b/el-GR/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/el-GR/Qtractor.po b/el-GR/Qtractor.po
index fdaa731..0a2210e 100644
--- a/el-GR/Qtractor.po
+++ b/el-GR/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/el-GR/Revision_History.po b/el-GR/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/el-GR/Revision_History.po
+++ b/el-GR/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/el-GR/Rosegarden.po b/el-GR/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/el-GR/Rosegarden.po
+++ b/el-GR/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/el-GR/Solfege.po b/el-GR/Solfege.po
index 673c88c..8110ddb 100644
--- a/el-GR/Solfege.po
+++ b/el-GR/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/el-GR/Sound_Cards.po b/el-GR/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/el-GR/Sound_Cards.po
+++ b/el-GR/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/el-GR/SuperCollider/SuperCollider-Basic_Programming.po b/el-GR/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/el-GR/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/el-GR/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/el-GR/SuperCollider/SuperCollider.po b/el-GR/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/el-GR/SuperCollider/SuperCollider.po
+++ b/el-GR/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/en-US/Musicians_Guide.xml b/en-US/Musicians_Guide.xml
index 703c3ff..1c77688 100644
--- a/en-US/Musicians_Guide.xml
+++ b/en-US/Musicians_Guide.xml
@@ -16,7 +16,7 @@
SuperCollider/SuperCollider-Composing.xml : lines 24, 25, and 26
-->
-<book status="draft">
+<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- Start Chapters -->
diff --git a/es-ES/Ardour.po b/es-ES/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/es-ES/Ardour.po
+++ b/es-ES/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/es-ES/Audacity.po b/es-ES/Audacity.po
index cb97802..0e4ae65 100644
--- a/es-ES/Audacity.po
+++ b/es-ES/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/es-ES/Audio_Vocabulary.po b/es-ES/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/es-ES/Audio_Vocabulary.po
+++ b/es-ES/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/es-ES/Digital_Audio_Workstations.po b/es-ES/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/es-ES/Digital_Audio_Workstations.po
+++ b/es-ES/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/es-ES/LilyPond/LilyPond-counterpoint.po b/es-ES/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/es-ES/LilyPond/LilyPond-counterpoint.po
+++ b/es-ES/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/es-ES/LilyPond/LilyPond-orchestra.po b/es-ES/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/es-ES/LilyPond/LilyPond-orchestra.po
+++ b/es-ES/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/es-ES/LilyPond/LilyPond-piano.po b/es-ES/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/es-ES/LilyPond/LilyPond-piano.po
+++ b/es-ES/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/es-ES/LilyPond/LilyPond-syntax.po b/es-ES/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/es-ES/LilyPond/LilyPond-syntax.po
+++ b/es-ES/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/es-ES/Planet_CCRMA_at_Home.po b/es-ES/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/es-ES/Planet_CCRMA_at_Home.po
+++ b/es-ES/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/es-ES/Qtractor.po b/es-ES/Qtractor.po
index fdaa731..0a2210e 100644
--- a/es-ES/Qtractor.po
+++ b/es-ES/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/es-ES/Revision_History.po b/es-ES/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/es-ES/Revision_History.po
+++ b/es-ES/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/es-ES/Rosegarden.po b/es-ES/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/es-ES/Rosegarden.po
+++ b/es-ES/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/es-ES/Solfege.po b/es-ES/Solfege.po
index 673c88c..8110ddb 100644
--- a/es-ES/Solfege.po
+++ b/es-ES/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/es-ES/Sound_Cards.po b/es-ES/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/es-ES/Sound_Cards.po
+++ b/es-ES/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/es-ES/SuperCollider/SuperCollider-Basic_Programming.po b/es-ES/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/es-ES/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/es-ES/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/es-ES/SuperCollider/SuperCollider.po b/es-ES/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/es-ES/SuperCollider/SuperCollider.po
+++ b/es-ES/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/fr-FR/Ardour.po b/fr-FR/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/fr-FR/Ardour.po
+++ b/fr-FR/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/fr-FR/Audacity.po b/fr-FR/Audacity.po
index cb97802..0e4ae65 100644
--- a/fr-FR/Audacity.po
+++ b/fr-FR/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/fr-FR/Audio_Vocabulary.po b/fr-FR/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/fr-FR/Audio_Vocabulary.po
+++ b/fr-FR/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/fr-FR/Digital_Audio_Workstations.po b/fr-FR/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/fr-FR/Digital_Audio_Workstations.po
+++ b/fr-FR/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/fr-FR/LilyPond/LilyPond-counterpoint.po b/fr-FR/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/fr-FR/LilyPond/LilyPond-counterpoint.po
+++ b/fr-FR/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/fr-FR/LilyPond/LilyPond-orchestra.po b/fr-FR/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/fr-FR/LilyPond/LilyPond-orchestra.po
+++ b/fr-FR/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/fr-FR/LilyPond/LilyPond-piano.po b/fr-FR/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/fr-FR/LilyPond/LilyPond-piano.po
+++ b/fr-FR/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/fr-FR/LilyPond/LilyPond-syntax.po b/fr-FR/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/fr-FR/LilyPond/LilyPond-syntax.po
+++ b/fr-FR/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/fr-FR/Planet_CCRMA_at_Home.po b/fr-FR/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/fr-FR/Planet_CCRMA_at_Home.po
+++ b/fr-FR/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/fr-FR/Qtractor.po b/fr-FR/Qtractor.po
index fdaa731..0a2210e 100644
--- a/fr-FR/Qtractor.po
+++ b/fr-FR/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/fr-FR/Revision_History.po b/fr-FR/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/fr-FR/Revision_History.po
+++ b/fr-FR/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/fr-FR/Rosegarden.po b/fr-FR/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/fr-FR/Rosegarden.po
+++ b/fr-FR/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/fr-FR/Solfege.po b/fr-FR/Solfege.po
index 673c88c..8110ddb 100644
--- a/fr-FR/Solfege.po
+++ b/fr-FR/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/fr-FR/Sound_Cards.po b/fr-FR/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/fr-FR/Sound_Cards.po
+++ b/fr-FR/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/fr-FR/SuperCollider/SuperCollider-Basic_Programming.po b/fr-FR/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/fr-FR/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/fr-FR/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/fr-FR/SuperCollider/SuperCollider.po b/fr-FR/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/fr-FR/SuperCollider/SuperCollider.po
+++ b/fr-FR/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/gu-IN/Ardour.po b/gu-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/gu-IN/Ardour.po
+++ b/gu-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/gu-IN/Audacity.po b/gu-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/gu-IN/Audacity.po
+++ b/gu-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/gu-IN/Audio_Vocabulary.po b/gu-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/gu-IN/Audio_Vocabulary.po
+++ b/gu-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/gu-IN/Digital_Audio_Workstations.po b/gu-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/gu-IN/Digital_Audio_Workstations.po
+++ b/gu-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/gu-IN/LilyPond/LilyPond-counterpoint.po b/gu-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/gu-IN/LilyPond/LilyPond-counterpoint.po
+++ b/gu-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/gu-IN/LilyPond/LilyPond-orchestra.po b/gu-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/gu-IN/LilyPond/LilyPond-orchestra.po
+++ b/gu-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/gu-IN/LilyPond/LilyPond-piano.po b/gu-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/gu-IN/LilyPond/LilyPond-piano.po
+++ b/gu-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/gu-IN/LilyPond/LilyPond-syntax.po b/gu-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/gu-IN/LilyPond/LilyPond-syntax.po
+++ b/gu-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/gu-IN/Planet_CCRMA_at_Home.po b/gu-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/gu-IN/Planet_CCRMA_at_Home.po
+++ b/gu-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/gu-IN/Qtractor.po b/gu-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/gu-IN/Qtractor.po
+++ b/gu-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/gu-IN/Revision_History.po b/gu-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/gu-IN/Revision_History.po
+++ b/gu-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/gu-IN/Rosegarden.po b/gu-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/gu-IN/Rosegarden.po
+++ b/gu-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/gu-IN/Solfege.po b/gu-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/gu-IN/Solfege.po
+++ b/gu-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/gu-IN/Sound_Cards.po b/gu-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/gu-IN/Sound_Cards.po
+++ b/gu-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/gu-IN/SuperCollider/SuperCollider-Basic_Programming.po b/gu-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/gu-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/gu-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/gu-IN/SuperCollider/SuperCollider.po b/gu-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/gu-IN/SuperCollider/SuperCollider.po
+++ b/gu-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/hi-IN/Ardour.po b/hi-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/hi-IN/Ardour.po
+++ b/hi-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/hi-IN/Audacity.po b/hi-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/hi-IN/Audacity.po
+++ b/hi-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/hi-IN/Audio_Vocabulary.po b/hi-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/hi-IN/Audio_Vocabulary.po
+++ b/hi-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/hi-IN/Digital_Audio_Workstations.po b/hi-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/hi-IN/Digital_Audio_Workstations.po
+++ b/hi-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/hi-IN/LilyPond/LilyPond-counterpoint.po b/hi-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/hi-IN/LilyPond/LilyPond-counterpoint.po
+++ b/hi-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/hi-IN/LilyPond/LilyPond-orchestra.po b/hi-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/hi-IN/LilyPond/LilyPond-orchestra.po
+++ b/hi-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/hi-IN/LilyPond/LilyPond-piano.po b/hi-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/hi-IN/LilyPond/LilyPond-piano.po
+++ b/hi-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/hi-IN/LilyPond/LilyPond-syntax.po b/hi-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/hi-IN/LilyPond/LilyPond-syntax.po
+++ b/hi-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/hi-IN/Planet_CCRMA_at_Home.po b/hi-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/hi-IN/Planet_CCRMA_at_Home.po
+++ b/hi-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/hi-IN/Qtractor.po b/hi-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/hi-IN/Qtractor.po
+++ b/hi-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/hi-IN/Revision_History.po b/hi-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/hi-IN/Revision_History.po
+++ b/hi-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/hi-IN/Rosegarden.po b/hi-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/hi-IN/Rosegarden.po
+++ b/hi-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/hi-IN/Solfege.po b/hi-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/hi-IN/Solfege.po
+++ b/hi-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/hi-IN/Sound_Cards.po b/hi-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/hi-IN/Sound_Cards.po
+++ b/hi-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/hi-IN/SuperCollider/SuperCollider-Basic_Programming.po b/hi-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/hi-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/hi-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/hi-IN/SuperCollider/SuperCollider.po b/hi-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/hi-IN/SuperCollider/SuperCollider.po
+++ b/hi-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/id-ID/Ardour.po b/id-ID/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/id-ID/Ardour.po
+++ b/id-ID/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/id-ID/Audacity.po b/id-ID/Audacity.po
index cb97802..0e4ae65 100644
--- a/id-ID/Audacity.po
+++ b/id-ID/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/id-ID/Audio_Vocabulary.po b/id-ID/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/id-ID/Audio_Vocabulary.po
+++ b/id-ID/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/id-ID/Digital_Audio_Workstations.po b/id-ID/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/id-ID/Digital_Audio_Workstations.po
+++ b/id-ID/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/id-ID/LilyPond/LilyPond-counterpoint.po b/id-ID/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/id-ID/LilyPond/LilyPond-counterpoint.po
+++ b/id-ID/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/id-ID/LilyPond/LilyPond-orchestra.po b/id-ID/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/id-ID/LilyPond/LilyPond-orchestra.po
+++ b/id-ID/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/id-ID/LilyPond/LilyPond-piano.po b/id-ID/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/id-ID/LilyPond/LilyPond-piano.po
+++ b/id-ID/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/id-ID/LilyPond/LilyPond-syntax.po b/id-ID/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/id-ID/LilyPond/LilyPond-syntax.po
+++ b/id-ID/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/id-ID/Planet_CCRMA_at_Home.po b/id-ID/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/id-ID/Planet_CCRMA_at_Home.po
+++ b/id-ID/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/id-ID/Qtractor.po b/id-ID/Qtractor.po
index fdaa731..0a2210e 100644
--- a/id-ID/Qtractor.po
+++ b/id-ID/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/id-ID/Revision_History.po b/id-ID/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/id-ID/Revision_History.po
+++ b/id-ID/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/id-ID/Rosegarden.po b/id-ID/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/id-ID/Rosegarden.po
+++ b/id-ID/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/id-ID/Solfege.po b/id-ID/Solfege.po
index 673c88c..8110ddb 100644
--- a/id-ID/Solfege.po
+++ b/id-ID/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/id-ID/Sound_Cards.po b/id-ID/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/id-ID/Sound_Cards.po
+++ b/id-ID/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/id-ID/SuperCollider/SuperCollider-Basic_Programming.po b/id-ID/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/id-ID/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/id-ID/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/id-ID/SuperCollider/SuperCollider.po b/id-ID/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/id-ID/SuperCollider/SuperCollider.po
+++ b/id-ID/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/it-IT/Ardour.po b/it-IT/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/it-IT/Ardour.po
+++ b/it-IT/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/it-IT/Audacity.po b/it-IT/Audacity.po
index cb97802..0e4ae65 100644
--- a/it-IT/Audacity.po
+++ b/it-IT/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/it-IT/Audio_Vocabulary.po b/it-IT/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/it-IT/Audio_Vocabulary.po
+++ b/it-IT/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/it-IT/Digital_Audio_Workstations.po b/it-IT/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/it-IT/Digital_Audio_Workstations.po
+++ b/it-IT/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/it-IT/LilyPond/LilyPond-counterpoint.po b/it-IT/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/it-IT/LilyPond/LilyPond-counterpoint.po
+++ b/it-IT/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/it-IT/LilyPond/LilyPond-orchestra.po b/it-IT/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/it-IT/LilyPond/LilyPond-orchestra.po
+++ b/it-IT/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/it-IT/LilyPond/LilyPond-piano.po b/it-IT/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/it-IT/LilyPond/LilyPond-piano.po
+++ b/it-IT/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/it-IT/LilyPond/LilyPond-syntax.po b/it-IT/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/it-IT/LilyPond/LilyPond-syntax.po
+++ b/it-IT/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/it-IT/Planet_CCRMA_at_Home.po b/it-IT/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/it-IT/Planet_CCRMA_at_Home.po
+++ b/it-IT/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/it-IT/Qtractor.po b/it-IT/Qtractor.po
index fdaa731..0a2210e 100644
--- a/it-IT/Qtractor.po
+++ b/it-IT/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/it-IT/Revision_History.po b/it-IT/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/it-IT/Revision_History.po
+++ b/it-IT/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/it-IT/Rosegarden.po b/it-IT/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/it-IT/Rosegarden.po
+++ b/it-IT/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/it-IT/Solfege.po b/it-IT/Solfege.po
index 673c88c..8110ddb 100644
--- a/it-IT/Solfege.po
+++ b/it-IT/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/it-IT/Sound_Cards.po b/it-IT/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/it-IT/Sound_Cards.po
+++ b/it-IT/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/it-IT/SuperCollider/SuperCollider-Basic_Programming.po b/it-IT/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/it-IT/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/it-IT/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/it-IT/SuperCollider/SuperCollider.po b/it-IT/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/it-IT/SuperCollider/SuperCollider.po
+++ b/it-IT/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/ja-JP/Ardour.po b/ja-JP/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/ja-JP/Ardour.po
+++ b/ja-JP/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/ja-JP/Audacity.po b/ja-JP/Audacity.po
index cb97802..0e4ae65 100644
--- a/ja-JP/Audacity.po
+++ b/ja-JP/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/ja-JP/Audio_Vocabulary.po b/ja-JP/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/ja-JP/Audio_Vocabulary.po
+++ b/ja-JP/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/ja-JP/Digital_Audio_Workstations.po b/ja-JP/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/ja-JP/Digital_Audio_Workstations.po
+++ b/ja-JP/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/ja-JP/LilyPond/LilyPond-counterpoint.po b/ja-JP/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/ja-JP/LilyPond/LilyPond-counterpoint.po
+++ b/ja-JP/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/ja-JP/LilyPond/LilyPond-orchestra.po b/ja-JP/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/ja-JP/LilyPond/LilyPond-orchestra.po
+++ b/ja-JP/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/ja-JP/LilyPond/LilyPond-piano.po b/ja-JP/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/ja-JP/LilyPond/LilyPond-piano.po
+++ b/ja-JP/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/ja-JP/LilyPond/LilyPond-syntax.po b/ja-JP/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/ja-JP/LilyPond/LilyPond-syntax.po
+++ b/ja-JP/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/ja-JP/Planet_CCRMA_at_Home.po b/ja-JP/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/ja-JP/Planet_CCRMA_at_Home.po
+++ b/ja-JP/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/ja-JP/Qtractor.po b/ja-JP/Qtractor.po
index fdaa731..0a2210e 100644
--- a/ja-JP/Qtractor.po
+++ b/ja-JP/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/ja-JP/Revision_History.po b/ja-JP/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/ja-JP/Revision_History.po
+++ b/ja-JP/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/ja-JP/Rosegarden.po b/ja-JP/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/ja-JP/Rosegarden.po
+++ b/ja-JP/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/ja-JP/Solfege.po b/ja-JP/Solfege.po
index 673c88c..8110ddb 100644
--- a/ja-JP/Solfege.po
+++ b/ja-JP/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/ja-JP/Sound_Cards.po b/ja-JP/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/ja-JP/Sound_Cards.po
+++ b/ja-JP/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/ja-JP/SuperCollider/SuperCollider-Basic_Programming.po b/ja-JP/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/ja-JP/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/ja-JP/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/ja-JP/SuperCollider/SuperCollider.po b/ja-JP/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/ja-JP/SuperCollider/SuperCollider.po
+++ b/ja-JP/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/kn-IN/Ardour.po b/kn-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/kn-IN/Ardour.po
+++ b/kn-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/kn-IN/Audacity.po b/kn-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/kn-IN/Audacity.po
+++ b/kn-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/kn-IN/Audio_Vocabulary.po b/kn-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/kn-IN/Audio_Vocabulary.po
+++ b/kn-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/kn-IN/Digital_Audio_Workstations.po b/kn-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/kn-IN/Digital_Audio_Workstations.po
+++ b/kn-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/kn-IN/LilyPond/LilyPond-counterpoint.po b/kn-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/kn-IN/LilyPond/LilyPond-counterpoint.po
+++ b/kn-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/kn-IN/LilyPond/LilyPond-orchestra.po b/kn-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/kn-IN/LilyPond/LilyPond-orchestra.po
+++ b/kn-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/kn-IN/LilyPond/LilyPond-piano.po b/kn-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/kn-IN/LilyPond/LilyPond-piano.po
+++ b/kn-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/kn-IN/LilyPond/LilyPond-syntax.po b/kn-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/kn-IN/LilyPond/LilyPond-syntax.po
+++ b/kn-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/kn-IN/Planet_CCRMA_at_Home.po b/kn-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/kn-IN/Planet_CCRMA_at_Home.po
+++ b/kn-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/kn-IN/Qtractor.po b/kn-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/kn-IN/Qtractor.po
+++ b/kn-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/kn-IN/Revision_History.po b/kn-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/kn-IN/Revision_History.po
+++ b/kn-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/kn-IN/Rosegarden.po b/kn-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/kn-IN/Rosegarden.po
+++ b/kn-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/kn-IN/Solfege.po b/kn-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/kn-IN/Solfege.po
+++ b/kn-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/kn-IN/Sound_Cards.po b/kn-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/kn-IN/Sound_Cards.po
+++ b/kn-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/kn-IN/SuperCollider/SuperCollider-Basic_Programming.po b/kn-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/kn-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/kn-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/kn-IN/SuperCollider/SuperCollider.po b/kn-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/kn-IN/SuperCollider/SuperCollider.po
+++ b/kn-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/ml-IN/Ardour.po b/ml-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/ml-IN/Ardour.po
+++ b/ml-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/ml-IN/Audacity.po b/ml-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/ml-IN/Audacity.po
+++ b/ml-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/ml-IN/Audio_Vocabulary.po b/ml-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/ml-IN/Audio_Vocabulary.po
+++ b/ml-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/ml-IN/Digital_Audio_Workstations.po b/ml-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/ml-IN/Digital_Audio_Workstations.po
+++ b/ml-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/ml-IN/LilyPond/LilyPond-counterpoint.po b/ml-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/ml-IN/LilyPond/LilyPond-counterpoint.po
+++ b/ml-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/ml-IN/LilyPond/LilyPond-orchestra.po b/ml-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/ml-IN/LilyPond/LilyPond-orchestra.po
+++ b/ml-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/ml-IN/LilyPond/LilyPond-piano.po b/ml-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/ml-IN/LilyPond/LilyPond-piano.po
+++ b/ml-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/ml-IN/LilyPond/LilyPond-syntax.po b/ml-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/ml-IN/LilyPond/LilyPond-syntax.po
+++ b/ml-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/ml-IN/Planet_CCRMA_at_Home.po b/ml-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/ml-IN/Planet_CCRMA_at_Home.po
+++ b/ml-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/ml-IN/Qtractor.po b/ml-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/ml-IN/Qtractor.po
+++ b/ml-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/ml-IN/Revision_History.po b/ml-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/ml-IN/Revision_History.po
+++ b/ml-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/ml-IN/Rosegarden.po b/ml-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/ml-IN/Rosegarden.po
+++ b/ml-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/ml-IN/Solfege.po b/ml-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/ml-IN/Solfege.po
+++ b/ml-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/ml-IN/Sound_Cards.po b/ml-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/ml-IN/Sound_Cards.po
+++ b/ml-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/ml-IN/SuperCollider/SuperCollider-Basic_Programming.po b/ml-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/ml-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/ml-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/ml-IN/SuperCollider/SuperCollider.po b/ml-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/ml-IN/SuperCollider/SuperCollider.po
+++ b/ml-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/mr-IN/Ardour.po b/mr-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/mr-IN/Ardour.po
+++ b/mr-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/mr-IN/Audacity.po b/mr-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/mr-IN/Audacity.po
+++ b/mr-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/mr-IN/Audio_Vocabulary.po b/mr-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/mr-IN/Audio_Vocabulary.po
+++ b/mr-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/mr-IN/Digital_Audio_Workstations.po b/mr-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/mr-IN/Digital_Audio_Workstations.po
+++ b/mr-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/mr-IN/LilyPond/LilyPond-counterpoint.po b/mr-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/mr-IN/LilyPond/LilyPond-counterpoint.po
+++ b/mr-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/mr-IN/LilyPond/LilyPond-orchestra.po b/mr-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/mr-IN/LilyPond/LilyPond-orchestra.po
+++ b/mr-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/mr-IN/LilyPond/LilyPond-piano.po b/mr-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/mr-IN/LilyPond/LilyPond-piano.po
+++ b/mr-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/mr-IN/LilyPond/LilyPond-syntax.po b/mr-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/mr-IN/LilyPond/LilyPond-syntax.po
+++ b/mr-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/mr-IN/Planet_CCRMA_at_Home.po b/mr-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/mr-IN/Planet_CCRMA_at_Home.po
+++ b/mr-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/mr-IN/Qtractor.po b/mr-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/mr-IN/Qtractor.po
+++ b/mr-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/mr-IN/Revision_History.po b/mr-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/mr-IN/Revision_History.po
+++ b/mr-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/mr-IN/Rosegarden.po b/mr-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/mr-IN/Rosegarden.po
+++ b/mr-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/mr-IN/Solfege.po b/mr-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/mr-IN/Solfege.po
+++ b/mr-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/mr-IN/Sound_Cards.po b/mr-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/mr-IN/Sound_Cards.po
+++ b/mr-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/mr-IN/SuperCollider/SuperCollider-Basic_Programming.po b/mr-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/mr-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/mr-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/mr-IN/SuperCollider/SuperCollider.po b/mr-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/mr-IN/SuperCollider/SuperCollider.po
+++ b/mr-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/nl-NL/Ardour.po b/nl-NL/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/nl-NL/Ardour.po
+++ b/nl-NL/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/nl-NL/Audacity.po b/nl-NL/Audacity.po
index cb97802..0e4ae65 100644
--- a/nl-NL/Audacity.po
+++ b/nl-NL/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/nl-NL/Audio_Vocabulary.po b/nl-NL/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/nl-NL/Audio_Vocabulary.po
+++ b/nl-NL/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/nl-NL/Digital_Audio_Workstations.po b/nl-NL/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/nl-NL/Digital_Audio_Workstations.po
+++ b/nl-NL/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/nl-NL/LilyPond/LilyPond-counterpoint.po b/nl-NL/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/nl-NL/LilyPond/LilyPond-counterpoint.po
+++ b/nl-NL/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/nl-NL/LilyPond/LilyPond-orchestra.po b/nl-NL/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/nl-NL/LilyPond/LilyPond-orchestra.po
+++ b/nl-NL/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/nl-NL/LilyPond/LilyPond-piano.po b/nl-NL/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/nl-NL/LilyPond/LilyPond-piano.po
+++ b/nl-NL/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/nl-NL/LilyPond/LilyPond-syntax.po b/nl-NL/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/nl-NL/LilyPond/LilyPond-syntax.po
+++ b/nl-NL/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/nl-NL/Planet_CCRMA_at_Home.po b/nl-NL/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/nl-NL/Planet_CCRMA_at_Home.po
+++ b/nl-NL/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/nl-NL/Qtractor.po b/nl-NL/Qtractor.po
index fdaa731..0a2210e 100644
--- a/nl-NL/Qtractor.po
+++ b/nl-NL/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/nl-NL/Revision_History.po b/nl-NL/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/nl-NL/Revision_History.po
+++ b/nl-NL/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/nl-NL/Rosegarden.po b/nl-NL/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/nl-NL/Rosegarden.po
+++ b/nl-NL/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/nl-NL/Solfege.po b/nl-NL/Solfege.po
index 673c88c..8110ddb 100644
--- a/nl-NL/Solfege.po
+++ b/nl-NL/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/nl-NL/Sound_Cards.po b/nl-NL/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/nl-NL/Sound_Cards.po
+++ b/nl-NL/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/nl-NL/SuperCollider/SuperCollider-Basic_Programming.po b/nl-NL/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/nl-NL/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/nl-NL/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/nl-NL/SuperCollider/SuperCollider.po b/nl-NL/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/nl-NL/SuperCollider/SuperCollider.po
+++ b/nl-NL/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/or-IN/Ardour.po b/or-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/or-IN/Ardour.po
+++ b/or-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/or-IN/Audacity.po b/or-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/or-IN/Audacity.po
+++ b/or-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/or-IN/Audio_Vocabulary.po b/or-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/or-IN/Audio_Vocabulary.po
+++ b/or-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/or-IN/Digital_Audio_Workstations.po b/or-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/or-IN/Digital_Audio_Workstations.po
+++ b/or-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/or-IN/LilyPond/LilyPond-counterpoint.po b/or-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/or-IN/LilyPond/LilyPond-counterpoint.po
+++ b/or-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/or-IN/LilyPond/LilyPond-orchestra.po b/or-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/or-IN/LilyPond/LilyPond-orchestra.po
+++ b/or-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/or-IN/LilyPond/LilyPond-piano.po b/or-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/or-IN/LilyPond/LilyPond-piano.po
+++ b/or-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/or-IN/LilyPond/LilyPond-syntax.po b/or-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/or-IN/LilyPond/LilyPond-syntax.po
+++ b/or-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/or-IN/Planet_CCRMA_at_Home.po b/or-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/or-IN/Planet_CCRMA_at_Home.po
+++ b/or-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/or-IN/Qtractor.po b/or-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/or-IN/Qtractor.po
+++ b/or-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/or-IN/Revision_History.po b/or-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/or-IN/Revision_History.po
+++ b/or-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/or-IN/Rosegarden.po b/or-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/or-IN/Rosegarden.po
+++ b/or-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/or-IN/Solfege.po b/or-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/or-IN/Solfege.po
+++ b/or-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/or-IN/Sound_Cards.po b/or-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/or-IN/Sound_Cards.po
+++ b/or-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/or-IN/SuperCollider/SuperCollider-Basic_Programming.po b/or-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/or-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/or-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/or-IN/SuperCollider/SuperCollider.po b/or-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/or-IN/SuperCollider/SuperCollider.po
+++ b/or-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/pa-IN/Ardour.po b/pa-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/pa-IN/Ardour.po
+++ b/pa-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/pa-IN/Audacity.po b/pa-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/pa-IN/Audacity.po
+++ b/pa-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/pa-IN/Audio_Vocabulary.po b/pa-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/pa-IN/Audio_Vocabulary.po
+++ b/pa-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/pa-IN/Digital_Audio_Workstations.po b/pa-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/pa-IN/Digital_Audio_Workstations.po
+++ b/pa-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/pa-IN/LilyPond/LilyPond-counterpoint.po b/pa-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/pa-IN/LilyPond/LilyPond-counterpoint.po
+++ b/pa-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/pa-IN/LilyPond/LilyPond-orchestra.po b/pa-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/pa-IN/LilyPond/LilyPond-orchestra.po
+++ b/pa-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/pa-IN/LilyPond/LilyPond-piano.po b/pa-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/pa-IN/LilyPond/LilyPond-piano.po
+++ b/pa-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/pa-IN/LilyPond/LilyPond-syntax.po b/pa-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/pa-IN/LilyPond/LilyPond-syntax.po
+++ b/pa-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/pa-IN/Planet_CCRMA_at_Home.po b/pa-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/pa-IN/Planet_CCRMA_at_Home.po
+++ b/pa-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/pa-IN/Qtractor.po b/pa-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/pa-IN/Qtractor.po
+++ b/pa-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/pa-IN/Revision_History.po b/pa-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/pa-IN/Revision_History.po
+++ b/pa-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/pa-IN/Rosegarden.po b/pa-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/pa-IN/Rosegarden.po
+++ b/pa-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/pa-IN/Solfege.po b/pa-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/pa-IN/Solfege.po
+++ b/pa-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/pa-IN/Sound_Cards.po b/pa-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/pa-IN/Sound_Cards.po
+++ b/pa-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/pa-IN/SuperCollider/SuperCollider-Basic_Programming.po b/pa-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/pa-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/pa-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/pa-IN/SuperCollider/SuperCollider.po b/pa-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/pa-IN/SuperCollider/SuperCollider.po
+++ b/pa-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/pl-PL/Ardour.po b/pl-PL/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/pl-PL/Ardour.po
+++ b/pl-PL/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/pl-PL/Audacity.po b/pl-PL/Audacity.po
index cb97802..0e4ae65 100644
--- a/pl-PL/Audacity.po
+++ b/pl-PL/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/pl-PL/Audio_Vocabulary.po b/pl-PL/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/pl-PL/Audio_Vocabulary.po
+++ b/pl-PL/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/pl-PL/Digital_Audio_Workstations.po b/pl-PL/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/pl-PL/Digital_Audio_Workstations.po
+++ b/pl-PL/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/pl-PL/LilyPond/LilyPond-counterpoint.po b/pl-PL/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/pl-PL/LilyPond/LilyPond-counterpoint.po
+++ b/pl-PL/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/pl-PL/LilyPond/LilyPond-orchestra.po b/pl-PL/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/pl-PL/LilyPond/LilyPond-orchestra.po
+++ b/pl-PL/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/pl-PL/LilyPond/LilyPond-piano.po b/pl-PL/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/pl-PL/LilyPond/LilyPond-piano.po
+++ b/pl-PL/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/pl-PL/LilyPond/LilyPond-syntax.po b/pl-PL/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/pl-PL/LilyPond/LilyPond-syntax.po
+++ b/pl-PL/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/pl-PL/Planet_CCRMA_at_Home.po b/pl-PL/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/pl-PL/Planet_CCRMA_at_Home.po
+++ b/pl-PL/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/pl-PL/Qtractor.po b/pl-PL/Qtractor.po
index fdaa731..0a2210e 100644
--- a/pl-PL/Qtractor.po
+++ b/pl-PL/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/pl-PL/Revision_History.po b/pl-PL/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/pl-PL/Revision_History.po
+++ b/pl-PL/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/pl-PL/Rosegarden.po b/pl-PL/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/pl-PL/Rosegarden.po
+++ b/pl-PL/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/pl-PL/Solfege.po b/pl-PL/Solfege.po
index 673c88c..8110ddb 100644
--- a/pl-PL/Solfege.po
+++ b/pl-PL/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/pl-PL/Sound_Cards.po b/pl-PL/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/pl-PL/Sound_Cards.po
+++ b/pl-PL/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/pl-PL/SuperCollider/SuperCollider-Basic_Programming.po b/pl-PL/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/pl-PL/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/pl-PL/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/pl-PL/SuperCollider/SuperCollider.po b/pl-PL/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/pl-PL/SuperCollider/SuperCollider.po
+++ b/pl-PL/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/pot/Ardour.pot b/pot/Ardour.pot
index 766be5f..de96873 100644
--- a/pot/Ardour.pot
+++ b/pot/Ardour.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
-"PO-Revision-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -102,134 +102,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -239,7 +314,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -249,72 +324,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -324,12 +399,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -339,7 +414,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -354,7 +439,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -364,7 +449,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -499,7 +584,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -969,7 +1054,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1179,7 +1264,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1332,19 +1417,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2004,7 +2079,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2339,7 +2414,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2384,7 +2459,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2769,7 +2844,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/pot/Audacity.pot b/pot/Audacity.pot
index 4863afe..d719ad3 100644
--- a/pot/Audacity.pot
+++ b/pot/Audacity.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -89,7 +89,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -114,7 +114,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -279,15 +291,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
-msgid "0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+msgid "<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -302,7 +314,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -355,9 +367,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/pot/Audio_Vocabulary.pot b/pot/Audio_Vocabulary.pot
index 20bb4ca..a7cd5dd 100644
--- a/pot/Audio_Vocabulary.pot
+++ b/pot/Audio_Vocabulary.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -39,12 +39,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -57,6 +62,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -132,6 +147,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -142,6 +167,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -204,7 +239,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/pot/Author_Group.pot b/pot/Author_Group.pot
index ff6afba..5719a33 100644
--- a/pot/Author_Group.pot
+++ b/pot/Author_Group.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Book_Info.pot b/pot/Book_Info.pot
index 06e9e8b..210359d 100644
--- a/pot/Book_Info.pot
+++ b/pot/Book_Info.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Chapter.pot b/pot/Chapter.pot
index 298e0a1..0ee8bd6 100644
--- a/pot/Chapter.pot
+++ b/pot/Chapter.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Digital_Audio_Workstations.pot b/pot/Digital_Audio_Workstations.pot
index f634ac7..69eba67 100644
--- a/pot/Digital_Audio_Workstations.pot
+++ b/pot/Digital_Audio_Workstations.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -209,6 +209,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -219,6 +229,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -249,7 +269,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -289,17 +314,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -307,64 +337,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -372,9 +447,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -384,7 +494,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -394,7 +504,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -404,6 +514,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/pot/FluidSynth.pot b/pot/FluidSynth.pot
index 05e69b1..ace6a10 100644
--- a/pot/FluidSynth.pot
+++ b/pot/FluidSynth.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Frescobaldi.pot b/pot/Frescobaldi.pot
index 87589bd..c964c47 100644
--- a/pot/Frescobaldi.pot
+++ b/pot/Frescobaldi.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/LilyPond/LilyPond-counterpoint.pot b/pot/LilyPond/LilyPond-counterpoint.pot
index f4e7bc0..a6dd02e 100644
--- a/pot/LilyPond/LilyPond-counterpoint.pot
+++ b/pot/LilyPond/LilyPond-counterpoint.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -54,7 +54,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -194,7 +194,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -204,7 +204,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -319,7 +319,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/pot/LilyPond/LilyPond-orchestra.pot b/pot/LilyPond/LilyPond-orchestra.pot
index c12bd09..77386f2 100644
--- a/pot/LilyPond/LilyPond-orchestra.pot
+++ b/pot/LilyPond/LilyPond-orchestra.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -258,52 +258,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -595,7 +595,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -660,12 +660,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -685,12 +685,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -730,7 +730,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/pot/LilyPond/LilyPond-piano.pot b/pot/LilyPond/LilyPond-piano.pot
index 257d701..b334f59 100644
--- a/pot/LilyPond/LilyPond-piano.pot
+++ b/pot/LilyPond/LilyPond-piano.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -64,7 +64,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -330,12 +330,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -350,7 +350,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -380,12 +380,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -400,7 +400,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -526,14 +526,14 @@ msgid "\n"
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
""
msgstr ""
@@ -615,7 +615,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/pot/LilyPond/LilyPond-syntax.pot b/pot/LilyPond/LilyPond-syntax.pot
index edd18ff..b82cc83 100644
--- a/pot/LilyPond/LilyPond-syntax.pot
+++ b/pot/LilyPond/LilyPond-syntax.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -134,7 +134,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -199,17 +199,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/pot/LilyPond/LilyPond.pot b/pot/LilyPond/LilyPond.pot
index 12b2888..2be62e3 100644
--- a/pot/LilyPond/LilyPond.pot
+++ b/pot/LilyPond/LilyPond.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Musicians_Guide.pot b/pot/Musicians_Guide.pot
index 188dfa8..756bf7b 100644
--- a/pot/Musicians_Guide.pot
+++ b/pot/Musicians_Guide.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Planet_CCRMA_at_Home.pot b/pot/Planet_CCRMA_at_Home.pot
index 254c0e5..f9a055a 100644
--- a/pot/Planet_CCRMA_at_Home.pot
+++ b/pot/Planet_CCRMA_at_Home.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -149,12 +149,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/pot/Preface.pot b/pot/Preface.pot
index 7c49f85..b69678f 100644
--- a/pot/Preface.pot
+++ b/pot/Preface.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Qtractor.pot b/pot/Qtractor.pot
index 51d181a..ac19a40 100644
--- a/pot/Qtractor.pot
+++ b/pot/Qtractor.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
+"PO-Revision-Date: 2010-11-02T04:33:08\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -204,7 +204,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -494,7 +494,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -514,7 +514,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -554,7 +554,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -589,7 +589,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -625,7 +625,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -800,7 +800,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -900,7 +900,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -910,7 +910,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -940,7 +940,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -990,12 +990,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/pot/Real_Time_and_Low_Latency.pot b/pot/Real_Time_and_Low_Latency.pot
index 1c6d177..70c3aa0 100644
--- a/pot/Real_Time_and_Low_Latency.pot
+++ b/pot/Real_Time_and_Low_Latency.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/Revision_History.pot b/pot/Revision_History.pot
index c76ea30..63bf543 100644
--- a/pot/Revision_History.pot
+++ b/pot/Revision_History.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -69,12 +69,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -84,17 +84,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/pot/Rosegarden.pot b/pot/Rosegarden.pot
index abb1c53..f92ee59 100644
--- a/pot/Rosegarden.pot
+++ b/pot/Rosegarden.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -255,12 +255,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -295,7 +295,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -440,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -475,17 +475,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/pot/Solfege.pot b/pot/Solfege.pot
index 7d31bb8..d44f627 100644
--- a/pot/Solfege.pot
+++ b/pot/Solfege.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -119,7 +119,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/pot/Sound_Cards.pot b/pot/Sound_Cards.pot
index a962213..ae109ca 100644
--- a/pot/Sound_Cards.pot
+++ b/pot/Sound_Cards.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -149,7 +149,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/pot/Sound_Servers.pot b/pot/Sound_Servers.pot
index bcb8e28..a450519 100644
--- a/pot/Sound_Servers.pot
+++ b/pot/Sound_Servers.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
-"PO-Revision-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/SuperCollider/SuperCollider-Basic_Programming.pot b/pot/SuperCollider/SuperCollider-Basic_Programming.pot
index 8ceb40e..3d9122e 100644
--- a/pot/SuperCollider/SuperCollider-Basic_Programming.pot
+++ b/pot/SuperCollider/SuperCollider-Basic_Programming.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
-"PO-Revision-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -2182,7 +2182,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2192,7 +2192,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2202,7 +2202,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2212,7 +2212,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2568,8 +2568,8 @@ msgstr ""
#, no-c-format
msgid "\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2859,10 +2859,10 @@ msgstr ""
#, no-c-format
msgid "\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
""
msgstr ""
@@ -3844,8 +3844,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
""
msgstr ""
@@ -4047,8 +4047,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
""
msgstr ""
diff --git a/pot/SuperCollider/SuperCollider-Composing.pot b/pot/SuperCollider/SuperCollider-Composing.pot
index f55db70..8ceb86f 100644
--- a/pot/SuperCollider/SuperCollider-Composing.pot
+++ b/pot/SuperCollider/SuperCollider-Composing.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
-"PO-Revision-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/SuperCollider/SuperCollider-Exporting.pot b/pot/SuperCollider/SuperCollider-Exporting.pot
index f8a5479..919bc7c 100644
--- a/pot/SuperCollider/SuperCollider-Exporting.pot
+++ b/pot/SuperCollider/SuperCollider-Exporting.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
-"PO-Revision-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/pot/SuperCollider/SuperCollider.pot b/pot/SuperCollider/SuperCollider.pot
index 657e4bf..ce11eff 100644
--- a/pot/SuperCollider/SuperCollider.pot
+++ b/pot/SuperCollider/SuperCollider.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
-"PO-Revision-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
+"PO-Revision-Date: 2010-11-02T04:33:09\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -412,7 +412,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -456,12 +456,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/pt-BR/Ardour.po b/pt-BR/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/pt-BR/Ardour.po
+++ b/pt-BR/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/pt-BR/Audacity.po b/pt-BR/Audacity.po
index cb97802..0e4ae65 100644
--- a/pt-BR/Audacity.po
+++ b/pt-BR/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/pt-BR/Audio_Vocabulary.po b/pt-BR/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/pt-BR/Audio_Vocabulary.po
+++ b/pt-BR/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/pt-BR/Digital_Audio_Workstations.po b/pt-BR/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/pt-BR/Digital_Audio_Workstations.po
+++ b/pt-BR/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/pt-BR/LilyPond/LilyPond-counterpoint.po b/pt-BR/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/pt-BR/LilyPond/LilyPond-counterpoint.po
+++ b/pt-BR/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/pt-BR/LilyPond/LilyPond-orchestra.po b/pt-BR/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/pt-BR/LilyPond/LilyPond-orchestra.po
+++ b/pt-BR/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/pt-BR/LilyPond/LilyPond-piano.po b/pt-BR/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/pt-BR/LilyPond/LilyPond-piano.po
+++ b/pt-BR/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/pt-BR/LilyPond/LilyPond-syntax.po b/pt-BR/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/pt-BR/LilyPond/LilyPond-syntax.po
+++ b/pt-BR/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/pt-BR/Planet_CCRMA_at_Home.po b/pt-BR/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/pt-BR/Planet_CCRMA_at_Home.po
+++ b/pt-BR/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/pt-BR/Qtractor.po b/pt-BR/Qtractor.po
index fdaa731..0a2210e 100644
--- a/pt-BR/Qtractor.po
+++ b/pt-BR/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/pt-BR/Revision_History.po b/pt-BR/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/pt-BR/Revision_History.po
+++ b/pt-BR/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/pt-BR/Rosegarden.po b/pt-BR/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/pt-BR/Rosegarden.po
+++ b/pt-BR/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/pt-BR/Solfege.po b/pt-BR/Solfege.po
index 673c88c..8110ddb 100644
--- a/pt-BR/Solfege.po
+++ b/pt-BR/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/pt-BR/Sound_Cards.po b/pt-BR/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/pt-BR/Sound_Cards.po
+++ b/pt-BR/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/pt-BR/SuperCollider/SuperCollider-Basic_Programming.po b/pt-BR/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/pt-BR/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/pt-BR/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/pt-BR/SuperCollider/SuperCollider.po b/pt-BR/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/pt-BR/SuperCollider/SuperCollider.po
+++ b/pt-BR/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/pt-PT/Ardour.po b/pt-PT/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/pt-PT/Ardour.po
+++ b/pt-PT/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/pt-PT/Audacity.po b/pt-PT/Audacity.po
index cb97802..0e4ae65 100644
--- a/pt-PT/Audacity.po
+++ b/pt-PT/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/pt-PT/Audio_Vocabulary.po b/pt-PT/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/pt-PT/Audio_Vocabulary.po
+++ b/pt-PT/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/pt-PT/Digital_Audio_Workstations.po b/pt-PT/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/pt-PT/Digital_Audio_Workstations.po
+++ b/pt-PT/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/pt-PT/LilyPond/LilyPond-counterpoint.po b/pt-PT/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/pt-PT/LilyPond/LilyPond-counterpoint.po
+++ b/pt-PT/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/pt-PT/LilyPond/LilyPond-orchestra.po b/pt-PT/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/pt-PT/LilyPond/LilyPond-orchestra.po
+++ b/pt-PT/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/pt-PT/LilyPond/LilyPond-piano.po b/pt-PT/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/pt-PT/LilyPond/LilyPond-piano.po
+++ b/pt-PT/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/pt-PT/LilyPond/LilyPond-syntax.po b/pt-PT/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/pt-PT/LilyPond/LilyPond-syntax.po
+++ b/pt-PT/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/pt-PT/Planet_CCRMA_at_Home.po b/pt-PT/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/pt-PT/Planet_CCRMA_at_Home.po
+++ b/pt-PT/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/pt-PT/Qtractor.po b/pt-PT/Qtractor.po
index fdaa731..0a2210e 100644
--- a/pt-PT/Qtractor.po
+++ b/pt-PT/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/pt-PT/Revision_History.po b/pt-PT/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/pt-PT/Revision_History.po
+++ b/pt-PT/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/pt-PT/Rosegarden.po b/pt-PT/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/pt-PT/Rosegarden.po
+++ b/pt-PT/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/pt-PT/Solfege.po b/pt-PT/Solfege.po
index 673c88c..8110ddb 100644
--- a/pt-PT/Solfege.po
+++ b/pt-PT/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/pt-PT/Sound_Cards.po b/pt-PT/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/pt-PT/Sound_Cards.po
+++ b/pt-PT/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/pt-PT/SuperCollider/SuperCollider-Basic_Programming.po b/pt-PT/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/pt-PT/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/pt-PT/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/pt-PT/SuperCollider/SuperCollider.po b/pt-PT/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/pt-PT/SuperCollider/SuperCollider.po
+++ b/pt-PT/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/publican.cfg b/publican.cfg
index 8390db6..535cb20 100644
--- a/publican.cfg
+++ b/publican.cfg
@@ -6,6 +6,3 @@ type: Book
brand: fedora
docname: Musicians_Guide
-product: Fedora Draft Documentation
-version: 0.1
-web_version_label: UNUSED
diff --git a/ru-RU/Ardour.po b/ru-RU/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/ru-RU/Ardour.po
+++ b/ru-RU/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/ru-RU/Audacity.po b/ru-RU/Audacity.po
index cb97802..0e4ae65 100644
--- a/ru-RU/Audacity.po
+++ b/ru-RU/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/ru-RU/Audio_Vocabulary.po b/ru-RU/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/ru-RU/Audio_Vocabulary.po
+++ b/ru-RU/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/ru-RU/Digital_Audio_Workstations.po b/ru-RU/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/ru-RU/Digital_Audio_Workstations.po
+++ b/ru-RU/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/ru-RU/LilyPond/LilyPond-counterpoint.po b/ru-RU/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/ru-RU/LilyPond/LilyPond-counterpoint.po
+++ b/ru-RU/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/ru-RU/LilyPond/LilyPond-orchestra.po b/ru-RU/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/ru-RU/LilyPond/LilyPond-orchestra.po
+++ b/ru-RU/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/ru-RU/LilyPond/LilyPond-piano.po b/ru-RU/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/ru-RU/LilyPond/LilyPond-piano.po
+++ b/ru-RU/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/ru-RU/LilyPond/LilyPond-syntax.po b/ru-RU/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/ru-RU/LilyPond/LilyPond-syntax.po
+++ b/ru-RU/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/ru-RU/Planet_CCRMA_at_Home.po b/ru-RU/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/ru-RU/Planet_CCRMA_at_Home.po
+++ b/ru-RU/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/ru-RU/Qtractor.po b/ru-RU/Qtractor.po
index fdaa731..0a2210e 100644
--- a/ru-RU/Qtractor.po
+++ b/ru-RU/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/ru-RU/Revision_History.po b/ru-RU/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/ru-RU/Revision_History.po
+++ b/ru-RU/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/ru-RU/Rosegarden.po b/ru-RU/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/ru-RU/Rosegarden.po
+++ b/ru-RU/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/ru-RU/Solfege.po b/ru-RU/Solfege.po
index 673c88c..8110ddb 100644
--- a/ru-RU/Solfege.po
+++ b/ru-RU/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/ru-RU/Sound_Cards.po b/ru-RU/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/ru-RU/Sound_Cards.po
+++ b/ru-RU/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/ru-RU/SuperCollider/SuperCollider-Basic_Programming.po b/ru-RU/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/ru-RU/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/ru-RU/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/ru-RU/SuperCollider/SuperCollider.po b/ru-RU/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/ru-RU/SuperCollider/SuperCollider.po
+++ b/ru-RU/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Ardour.po b/sr-Latn-RS/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/sr-Latn-RS/Ardour.po
+++ b/sr-Latn-RS/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/sr-Latn-RS/Audacity.po b/sr-Latn-RS/Audacity.po
index cb97802..0e4ae65 100644
--- a/sr-Latn-RS/Audacity.po
+++ b/sr-Latn-RS/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Audio_Vocabulary.po b/sr-Latn-RS/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/sr-Latn-RS/Audio_Vocabulary.po
+++ b/sr-Latn-RS/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Digital_Audio_Workstations.po b/sr-Latn-RS/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/sr-Latn-RS/Digital_Audio_Workstations.po
+++ b/sr-Latn-RS/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/sr-Latn-RS/LilyPond/LilyPond-counterpoint.po b/sr-Latn-RS/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/sr-Latn-RS/LilyPond/LilyPond-counterpoint.po
+++ b/sr-Latn-RS/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/LilyPond/LilyPond-orchestra.po b/sr-Latn-RS/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/sr-Latn-RS/LilyPond/LilyPond-orchestra.po
+++ b/sr-Latn-RS/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/LilyPond/LilyPond-piano.po b/sr-Latn-RS/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/sr-Latn-RS/LilyPond/LilyPond-piano.po
+++ b/sr-Latn-RS/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/LilyPond/LilyPond-syntax.po b/sr-Latn-RS/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/sr-Latn-RS/LilyPond/LilyPond-syntax.po
+++ b/sr-Latn-RS/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/sr-Latn-RS/Planet_CCRMA_at_Home.po b/sr-Latn-RS/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/sr-Latn-RS/Planet_CCRMA_at_Home.po
+++ b/sr-Latn-RS/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Qtractor.po b/sr-Latn-RS/Qtractor.po
index fdaa731..0a2210e 100644
--- a/sr-Latn-RS/Qtractor.po
+++ b/sr-Latn-RS/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Revision_History.po b/sr-Latn-RS/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/sr-Latn-RS/Revision_History.po
+++ b/sr-Latn-RS/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/sr-Latn-RS/Rosegarden.po b/sr-Latn-RS/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/sr-Latn-RS/Rosegarden.po
+++ b/sr-Latn-RS/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Solfege.po b/sr-Latn-RS/Solfege.po
index 673c88c..8110ddb 100644
--- a/sr-Latn-RS/Solfege.po
+++ b/sr-Latn-RS/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/Sound_Cards.po b/sr-Latn-RS/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/sr-Latn-RS/Sound_Cards.po
+++ b/sr-Latn-RS/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/SuperCollider/SuperCollider-Basic_Programming.po b/sr-Latn-RS/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/sr-Latn-RS/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/sr-Latn-RS/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/sr-Latn-RS/SuperCollider/SuperCollider.po b/sr-Latn-RS/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/sr-Latn-RS/SuperCollider/SuperCollider.po
+++ b/sr-Latn-RS/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/sr-RS/Ardour.po b/sr-RS/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/sr-RS/Ardour.po
+++ b/sr-RS/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/sr-RS/Audacity.po b/sr-RS/Audacity.po
index cb97802..0e4ae65 100644
--- a/sr-RS/Audacity.po
+++ b/sr-RS/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/sr-RS/Audio_Vocabulary.po b/sr-RS/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/sr-RS/Audio_Vocabulary.po
+++ b/sr-RS/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/sr-RS/Digital_Audio_Workstations.po b/sr-RS/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/sr-RS/Digital_Audio_Workstations.po
+++ b/sr-RS/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/sr-RS/LilyPond/LilyPond-counterpoint.po b/sr-RS/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/sr-RS/LilyPond/LilyPond-counterpoint.po
+++ b/sr-RS/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/sr-RS/LilyPond/LilyPond-orchestra.po b/sr-RS/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/sr-RS/LilyPond/LilyPond-orchestra.po
+++ b/sr-RS/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/sr-RS/LilyPond/LilyPond-piano.po b/sr-RS/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/sr-RS/LilyPond/LilyPond-piano.po
+++ b/sr-RS/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/sr-RS/LilyPond/LilyPond-syntax.po b/sr-RS/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/sr-RS/LilyPond/LilyPond-syntax.po
+++ b/sr-RS/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/sr-RS/Planet_CCRMA_at_Home.po b/sr-RS/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/sr-RS/Planet_CCRMA_at_Home.po
+++ b/sr-RS/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/sr-RS/Qtractor.po b/sr-RS/Qtractor.po
index fdaa731..0a2210e 100644
--- a/sr-RS/Qtractor.po
+++ b/sr-RS/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/sr-RS/Revision_History.po b/sr-RS/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/sr-RS/Revision_History.po
+++ b/sr-RS/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/sr-RS/Rosegarden.po b/sr-RS/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/sr-RS/Rosegarden.po
+++ b/sr-RS/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/sr-RS/Solfege.po b/sr-RS/Solfege.po
index 673c88c..8110ddb 100644
--- a/sr-RS/Solfege.po
+++ b/sr-RS/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/sr-RS/Sound_Cards.po b/sr-RS/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/sr-RS/Sound_Cards.po
+++ b/sr-RS/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/sr-RS/SuperCollider/SuperCollider-Basic_Programming.po b/sr-RS/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/sr-RS/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/sr-RS/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/sr-RS/SuperCollider/SuperCollider.po b/sr-RS/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/sr-RS/SuperCollider/SuperCollider.po
+++ b/sr-RS/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/sv-SE/Ardour.po b/sv-SE/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/sv-SE/Ardour.po
+++ b/sv-SE/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/sv-SE/Audacity.po b/sv-SE/Audacity.po
index cb97802..0e4ae65 100644
--- a/sv-SE/Audacity.po
+++ b/sv-SE/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/sv-SE/Audio_Vocabulary.po b/sv-SE/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/sv-SE/Audio_Vocabulary.po
+++ b/sv-SE/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/sv-SE/Digital_Audio_Workstations.po b/sv-SE/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/sv-SE/Digital_Audio_Workstations.po
+++ b/sv-SE/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/sv-SE/LilyPond/LilyPond-counterpoint.po b/sv-SE/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/sv-SE/LilyPond/LilyPond-counterpoint.po
+++ b/sv-SE/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/sv-SE/LilyPond/LilyPond-orchestra.po b/sv-SE/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/sv-SE/LilyPond/LilyPond-orchestra.po
+++ b/sv-SE/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/sv-SE/LilyPond/LilyPond-piano.po b/sv-SE/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/sv-SE/LilyPond/LilyPond-piano.po
+++ b/sv-SE/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/sv-SE/LilyPond/LilyPond-syntax.po b/sv-SE/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/sv-SE/LilyPond/LilyPond-syntax.po
+++ b/sv-SE/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/sv-SE/Planet_CCRMA_at_Home.po b/sv-SE/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/sv-SE/Planet_CCRMA_at_Home.po
+++ b/sv-SE/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/sv-SE/Qtractor.po b/sv-SE/Qtractor.po
index fdaa731..0a2210e 100644
--- a/sv-SE/Qtractor.po
+++ b/sv-SE/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/sv-SE/Revision_History.po b/sv-SE/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/sv-SE/Revision_History.po
+++ b/sv-SE/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/sv-SE/Rosegarden.po b/sv-SE/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/sv-SE/Rosegarden.po
+++ b/sv-SE/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/sv-SE/Solfege.po b/sv-SE/Solfege.po
index 673c88c..8110ddb 100644
--- a/sv-SE/Solfege.po
+++ b/sv-SE/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/sv-SE/Sound_Cards.po b/sv-SE/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/sv-SE/Sound_Cards.po
+++ b/sv-SE/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/sv-SE/SuperCollider/SuperCollider-Basic_Programming.po b/sv-SE/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/sv-SE/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/sv-SE/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/sv-SE/SuperCollider/SuperCollider.po b/sv-SE/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/sv-SE/SuperCollider/SuperCollider.po
+++ b/sv-SE/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/ta-IN/Ardour.po b/ta-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/ta-IN/Ardour.po
+++ b/ta-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/ta-IN/Audacity.po b/ta-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/ta-IN/Audacity.po
+++ b/ta-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/ta-IN/Audio_Vocabulary.po b/ta-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/ta-IN/Audio_Vocabulary.po
+++ b/ta-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/ta-IN/Digital_Audio_Workstations.po b/ta-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/ta-IN/Digital_Audio_Workstations.po
+++ b/ta-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/ta-IN/LilyPond/LilyPond-counterpoint.po b/ta-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/ta-IN/LilyPond/LilyPond-counterpoint.po
+++ b/ta-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/ta-IN/LilyPond/LilyPond-orchestra.po b/ta-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/ta-IN/LilyPond/LilyPond-orchestra.po
+++ b/ta-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/ta-IN/LilyPond/LilyPond-piano.po b/ta-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/ta-IN/LilyPond/LilyPond-piano.po
+++ b/ta-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/ta-IN/LilyPond/LilyPond-syntax.po b/ta-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/ta-IN/LilyPond/LilyPond-syntax.po
+++ b/ta-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/ta-IN/Planet_CCRMA_at_Home.po b/ta-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/ta-IN/Planet_CCRMA_at_Home.po
+++ b/ta-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/ta-IN/Qtractor.po b/ta-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/ta-IN/Qtractor.po
+++ b/ta-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/ta-IN/Revision_History.po b/ta-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/ta-IN/Revision_History.po
+++ b/ta-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/ta-IN/Rosegarden.po b/ta-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/ta-IN/Rosegarden.po
+++ b/ta-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/ta-IN/Solfege.po b/ta-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/ta-IN/Solfege.po
+++ b/ta-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/ta-IN/Sound_Cards.po b/ta-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/ta-IN/Sound_Cards.po
+++ b/ta-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/ta-IN/SuperCollider/SuperCollider-Basic_Programming.po b/ta-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/ta-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/ta-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/ta-IN/SuperCollider/SuperCollider.po b/ta-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/ta-IN/SuperCollider/SuperCollider.po
+++ b/ta-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/te-IN/Ardour.po b/te-IN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/te-IN/Ardour.po
+++ b/te-IN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/te-IN/Audacity.po b/te-IN/Audacity.po
index cb97802..0e4ae65 100644
--- a/te-IN/Audacity.po
+++ b/te-IN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/te-IN/Audio_Vocabulary.po b/te-IN/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/te-IN/Audio_Vocabulary.po
+++ b/te-IN/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/te-IN/Digital_Audio_Workstations.po b/te-IN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/te-IN/Digital_Audio_Workstations.po
+++ b/te-IN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/te-IN/LilyPond/LilyPond-counterpoint.po b/te-IN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/te-IN/LilyPond/LilyPond-counterpoint.po
+++ b/te-IN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/te-IN/LilyPond/LilyPond-orchestra.po b/te-IN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/te-IN/LilyPond/LilyPond-orchestra.po
+++ b/te-IN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/te-IN/LilyPond/LilyPond-piano.po b/te-IN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/te-IN/LilyPond/LilyPond-piano.po
+++ b/te-IN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/te-IN/LilyPond/LilyPond-syntax.po b/te-IN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/te-IN/LilyPond/LilyPond-syntax.po
+++ b/te-IN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/te-IN/Planet_CCRMA_at_Home.po b/te-IN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/te-IN/Planet_CCRMA_at_Home.po
+++ b/te-IN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/te-IN/Qtractor.po b/te-IN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/te-IN/Qtractor.po
+++ b/te-IN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/te-IN/Revision_History.po b/te-IN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/te-IN/Revision_History.po
+++ b/te-IN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/te-IN/Rosegarden.po b/te-IN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/te-IN/Rosegarden.po
+++ b/te-IN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/te-IN/Solfege.po b/te-IN/Solfege.po
index 673c88c..8110ddb 100644
--- a/te-IN/Solfege.po
+++ b/te-IN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/te-IN/Sound_Cards.po b/te-IN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/te-IN/Sound_Cards.po
+++ b/te-IN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/te-IN/SuperCollider/SuperCollider-Basic_Programming.po b/te-IN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/te-IN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/te-IN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/te-IN/SuperCollider/SuperCollider.po b/te-IN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/te-IN/SuperCollider/SuperCollider.po
+++ b/te-IN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/uk-UA/Ardour.po b/uk-UA/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/uk-UA/Ardour.po
+++ b/uk-UA/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/uk-UA/Audacity.po b/uk-UA/Audacity.po
index cb97802..0e4ae65 100644
--- a/uk-UA/Audacity.po
+++ b/uk-UA/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/uk-UA/Audio_Vocabulary.po b/uk-UA/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/uk-UA/Audio_Vocabulary.po
+++ b/uk-UA/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/uk-UA/Digital_Audio_Workstations.po b/uk-UA/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/uk-UA/Digital_Audio_Workstations.po
+++ b/uk-UA/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/uk-UA/LilyPond/LilyPond-counterpoint.po b/uk-UA/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/uk-UA/LilyPond/LilyPond-counterpoint.po
+++ b/uk-UA/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/uk-UA/LilyPond/LilyPond-orchestra.po b/uk-UA/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/uk-UA/LilyPond/LilyPond-orchestra.po
+++ b/uk-UA/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/uk-UA/LilyPond/LilyPond-piano.po b/uk-UA/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/uk-UA/LilyPond/LilyPond-piano.po
+++ b/uk-UA/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/uk-UA/LilyPond/LilyPond-syntax.po b/uk-UA/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/uk-UA/LilyPond/LilyPond-syntax.po
+++ b/uk-UA/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/uk-UA/Planet_CCRMA_at_Home.po b/uk-UA/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/uk-UA/Planet_CCRMA_at_Home.po
+++ b/uk-UA/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/uk-UA/Qtractor.po b/uk-UA/Qtractor.po
index fdaa731..0a2210e 100644
--- a/uk-UA/Qtractor.po
+++ b/uk-UA/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/uk-UA/Revision_History.po b/uk-UA/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/uk-UA/Revision_History.po
+++ b/uk-UA/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/uk-UA/Rosegarden.po b/uk-UA/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/uk-UA/Rosegarden.po
+++ b/uk-UA/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/uk-UA/Solfege.po b/uk-UA/Solfege.po
index 673c88c..8110ddb 100644
--- a/uk-UA/Solfege.po
+++ b/uk-UA/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/uk-UA/Sound_Cards.po b/uk-UA/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/uk-UA/Sound_Cards.po
+++ b/uk-UA/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/uk-UA/SuperCollider/SuperCollider-Basic_Programming.po b/uk-UA/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/uk-UA/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/uk-UA/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/uk-UA/SuperCollider/SuperCollider.po b/uk-UA/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/uk-UA/SuperCollider/SuperCollider.po
+++ b/uk-UA/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/zh-CN/Ardour.po b/zh-CN/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/zh-CN/Ardour.po
+++ b/zh-CN/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/zh-CN/Audacity.po b/zh-CN/Audacity.po
index cb97802..0e4ae65 100644
--- a/zh-CN/Audacity.po
+++ b/zh-CN/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/zh-CN/Audio_Vocabulary.po b/zh-CN/Audio_Vocabulary.po
index a1e3d74..9274c68 100644
--- a/zh-CN/Audio_Vocabulary.po
+++ b/zh-CN/Audio_Vocabulary.po
@@ -1,16 +1,31 @@
# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Language: \n"
+
+#. Tag: title
+#, no-c-format
+msgid "Other Digital Audio Concepts"
+msgstr "其它数字音频概念"
+
+#. Tag: para
+#, no-c-format
+msgid "These terms are used in many different audio contexts. Understanding them is important to knowing how to operate audio equipment in general, whether computer-based or not."
+msgstr "很多不同的音频领域都会用到这些词汇。理解这些词汇对如何操作音频设备有着重要意义，而不管设备是否基于计算机。"
+
+#. Tag: title
+#, no-c-format
+msgid "MIDI Sequencer"
+msgstr "MIDI 音序器"
#. Tag: para
#, no-c-format
@@ -24,12 +39,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -42,6 +62,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -117,6 +147,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -127,6 +167,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -189,45 +239,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "<firstterm>Multiplexing</firstterm> allows you to connect multiple devices and applications to a single input or output. <application>QjackCtl</application> allows you to easily perform multiplexing. This may not seem important, but remember that only one connection is possible with a physical device like an audio interface. Before computers were used for music production, multiplexing required physical devices to split or combine the signals."
+msgid "Routing and multiplexing"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "Multichannel Audio"
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio channel</firstterm> is a single path of audio data. <firstterm>Multichannel audio</firstterm> is any audio which uses more than one channel simultaneously, allowing the transmission of more audio data than single-channel audio."
+msgid "Master bus inputs accept multiplexed audio from many sources."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Audio was originally recorded with only one channel, producing \"monophonic,\" or \"mono\" recordings. Beginning in the 1950s, stereophonic recordings, with two independent channels, began replacing monophonic recordings. Since humans have two independent ears, it makes sense to record and reproduce audio with two independent channels, involving two speakers. Most sound recordings available today are stereophonic, and people have found this mostly satisfying."
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a growing trend toward five- and seven-channel audio, driven primarily by \"surround-sound\" movies, and not widely available for music. Two \"surround-sound\" formats exist for music: DVD Audio (DVD-A) and Super Audio CD (SACD). The development of these formats, and the devices to use them, is held back by the proliferation of headphones with personal MP3 players, a general lack of desire for improvement in audio quality amongst consumers, and the copy-protection measures put in place by record labels. The result is that, while some consumers are willing to pay higher prices for DVD-A or SACD recordings, only a small number of recordings are available. Even if you buy a DVD-A or SACD-capable player, you would need to replace all of your audio equipment with models that support proprietary copy-protection software. Without this equipment, the player is often forbidden from outputting audio with a higher sample rate or sample format than a conventional audio C
D. None of these factors, unfortunately, seem like they will change in the near future."
+msgid "<firstterm>Multiplexing</firstterm> allows you to connect multiple devices and applications to a single input or output. <application>QjackCtl</application> allows you to easily perform multiplexing. This may not seem important, but remember that only one connection is possible with a physical device like an audio interface. Before computers were used for music production, multiplexing required physical devices to split or combine the signals."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Other Digital Audio Concepts"
-msgstr "其它数字音频概念"
+msgid "Multichannel Audio"
+msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "MIDI Sequencer"
-msgstr "MIDI 音序器"
+msgid "An <firstterm>audio channel</firstterm> is a single path of audio data. <firstterm>Multichannel audio</firstterm> is any audio which uses more than one channel simultaneously, allowing the transmission of more audio data than single-channel audio."
+msgstr ""
#. Tag: para
#, no-c-format
-msgid "These terms are used in many different audio contexts. Understanding them is important to knowing how to operate audio equipment in general, whether computer-based or not."
-msgstr "很多不同的音频领域都会用到这些词汇。理解这些词汇对如何操作音频设备有着重要意义，而不管设备是否基于计算机。"
+msgid "Audio was originally recorded with only one channel, producing \"monophonic,\" or \"mono\" recordings. Beginning in the 1950s, stereophonic recordings, with two independent channels, began replacing monophonic recordings. Since humans have two independent ears, it makes sense to record and reproduce audio with two independent channels, involving two speakers. Most sound recordings available today are stereophonic, and people have found this mostly satisfying."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There is a growing trend toward five- and seven-channel audio, driven primarily by \"surround-sound\" movies, and not widely available for music. Two \"surround-sound\" formats exist for music: DVD Audio (DVD-A) and Super Audio CD (SACD). The development of these formats, and the devices to use them, is held back by the proliferation of headphones with personal MP3 players, a general lack of desire for improvement in audio quality amongst consumers, and the copy-protection measures put in place by record labels. The result is that, while some consumers are willing to pay higher prices for DVD-A or SACD recordings, only a small number of recordings are available. Even if you buy a DVD-A or SACD-capable player, you would need to replace all of your audio equipment with models that support proprietary copy-protection software. Without this equipment, the player is often forbidden from outputting audio with a higher sample rate or sample format than a conventional audio C
D. None of these factors, unfortunately, seem like they will change in the near future."
+msgstr ""
diff --git a/zh-CN/Book_Info.po b/zh-CN/Book_Info.po
index e749def..aedbce6 100644
--- a/zh-CN/Book_Info.po
+++ b/zh-CN/Book_Info.po
@@ -1,32 +1,32 @@
# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Language: \n"
#. Tag: title
#, no-c-format
msgid "Musicians' Guide"
msgstr "乐手指南"
-#. Tag: productname
-#, no-c-format
-msgid "Fedora"
-msgstr "Fedora"
-
#. Tag: subtitle
#, no-c-format
msgid "A guide to Fedora Linux's audio creation and music capabilities."
msgstr "一份有关 Fedora Linux 音频创建和音乐方面性能的指南。"
+#. Tag: productname
+#, no-c-format
+msgid "Fedora"
+msgstr "Fedora"
+
#. Tag: para
#, no-c-format
msgid "This document explores some audio-creation and music activities possible with Fedora Linux. Computer audio concepts are explained, and a selection of programs are demonstrated with tutorials showing typical usage."
diff --git a/zh-CN/Digital_Audio_Workstations.po b/zh-CN/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/zh-CN/Digital_Audio_Workstations.po
+++ b/zh-CN/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/zh-CN/LilyPond/LilyPond-counterpoint.po b/zh-CN/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/zh-CN/LilyPond/LilyPond-counterpoint.po
+++ b/zh-CN/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/zh-CN/LilyPond/LilyPond-orchestra.po b/zh-CN/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/zh-CN/LilyPond/LilyPond-orchestra.po
+++ b/zh-CN/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/zh-CN/LilyPond/LilyPond-piano.po b/zh-CN/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/zh-CN/LilyPond/LilyPond-piano.po
+++ b/zh-CN/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/zh-CN/LilyPond/LilyPond-syntax.po b/zh-CN/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/zh-CN/LilyPond/LilyPond-syntax.po
+++ b/zh-CN/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/zh-CN/Musicians_Guide.po b/zh-CN/Musicians_Guide.po
index 5dceec7..9341e1f 100644
--- a/zh-CN/Musicians_Guide.po
+++ b/zh-CN/Musicians_Guide.po
@@ -1,28 +1,28 @@
# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Language: \n"
#. Tag: title
#, no-c-format
msgid "Linux Audio Basics"
msgstr "Linux 音频基础知识"
-#. Tag: title
-#, no-c-format
-msgid "Audio and Music Software"
-msgstr "音频及音乐软件"
-
#. Tag: para
#, no-c-format
msgid "asdf"
msgstr "asdf"
+
+#. Tag: title
+#, no-c-format
+msgid "Audio and Music Software"
+msgstr "音频及音乐软件"
diff --git a/zh-CN/Planet_CCRMA_at_Home.po b/zh-CN/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/zh-CN/Planet_CCRMA_at_Home.po
+++ b/zh-CN/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/zh-CN/Qtractor.po b/zh-CN/Qtractor.po
index fdaa731..0a2210e 100644
--- a/zh-CN/Qtractor.po
+++ b/zh-CN/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/zh-CN/Revision_History.po b/zh-CN/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/zh-CN/Revision_History.po
+++ b/zh-CN/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/zh-CN/Rosegarden.po b/zh-CN/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/zh-CN/Rosegarden.po
+++ b/zh-CN/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/zh-CN/Solfege.po b/zh-CN/Solfege.po
index 673c88c..8110ddb 100644
--- a/zh-CN/Solfege.po
+++ b/zh-CN/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/zh-CN/Sound_Cards.po b/zh-CN/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/zh-CN/Sound_Cards.po
+++ b/zh-CN/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/zh-CN/SuperCollider/SuperCollider-Basic_Programming.po b/zh-CN/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/zh-CN/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/zh-CN/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/zh-CN/SuperCollider/SuperCollider.po b/zh-CN/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/zh-CN/SuperCollider/SuperCollider.po
+++ b/zh-CN/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
diff --git a/zh-TW/Ardour.po b/zh-TW/Ardour.po
index 8e4d38f..8f0efce 100644
--- a/zh-TW/Ardour.po
+++ b/zh-TW/Ardour.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:41\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -103,134 +103,209 @@ msgstr ""
msgid "This section explains some of the graphical interface components that are unique to <application>Ardour</application>. Components that are consistent through most DAWs are explained in <xref linkend=\"sect-Musicians_Guide-DAW_Interface_Vocabulary\" />."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Ardour interface"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-editor_mixer.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shoes the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the \"Comments\" and outgoing connections buttons."
+msgid "Three graphical interface components specific to the Ardour interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-session_sidebar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the \"Regions\" tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgid "The <firstterm>editor mixer</firstterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-interface-toolbar.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> This image shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the \"snap mode\" menu (currently set to \"No Grid\"); the \"grid mode\" menu (currently set to \"Bars\"); and then \"edit point\" menu (currently set to \"Mouse\"). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: Select/Edit Object, and Select/Edit Range."
+msgid "The <firstterm>session sidebar</firstterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main toolbar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_overview\" /> illustrates three graphical interface components specific to the Ardour interface: the <firstterm>editor mixer</firstterm>, the <firstterm>session sidebar</firstterm>, and the main toolbar."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Setting up the Timeline"
+msgid "The Ardour editor mixer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Ardour editor mixer panel."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader control"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The fader level meter"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The panner"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The output connection button"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_editor_mixer\" /> shows the editor mixer, located at the left of the main <application>Ardour</application> window. The editor mixer shows only one mixer strip at a time. It shows the fader and its controls, in the middle of the mixer strip, the panner and its controls, at the bottom of the mixer strip, and the <guibutton>Comments</guibutton> and outgoing connections buttons."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Ardour session sidebar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks."
+msgid "The Ardour session sidebar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right-click to choose what you want them to display:"
+msgid "The tab strip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Bars:Beats\" displays the number of bars and beats (how to use it?)"
+msgid "The region list"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Minutes:Seconds\" displays the time since beginning of track (how to use it?)"
+msgid "<xref linkend=\"ardour_interface_session_sidebar\" /> shows the session sidebar, located at the right the main <application>Ardour</application> window. In this image, the <guilabel>Regions</guilabel> tab is selected, so the sidebar shows a list of regions currently in the session. You can see blue ones which were directly imported, white ones which were created from blue regions, and the arrows to the left of some blue regions, indicating that there are white-coloured sub-regions associated with those blue regions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The main Ardour toolbar"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Timecode\" displays frames-per-second timecode (usually for work with films)"
+msgid "The main Ardour toolbar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Samples\" displays the samples since start (how to use it?)"
+msgid "Tool selection buttons"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set the two clocks as desired (maybe turn one off if you only want one)"
+msgid "The <guibutton>select/edit object</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"snap mode\" menu is located between the timeline and the clocks."
+msgid "The <guibutton>select/edit range</guibutton> button"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This controls where regions may move. You will need to change these as you work with a session, depending on the current activity."
+msgid "The snap mode"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "left menu:"
+msgid "The grid mode"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The edit point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<xref linkend=\"ardour_interface_toolbar\" /> shows the main toolbar, located underneath the transport controls, and above the timeline and its rulers. In the middle of the toolbar are three unlabeled, but highly useful multiple-choice menus: the <guimenu>snap mode</guimenu> menu (currently set to <literal>No Grid</literal>); the <guimenu>grid mode</guimenu> menu (currently set to <literal>Bars</literal>); and then <guimenu>edit point</guimenu> menu (currently set to <literal>Mouse</literal>). To the left of these menus are the tool-selection buttons, the most important of which are the two left-most buttons: <guibutton>select/edit object</guibutton>, and <guibutton>select/edit range</guibutton>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Setting up the Timeline"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No Grid: regions can go wherever they want"
+msgid "At the top of the main <application>Ardour</application> window, to the right of the transport's toolbar, are two relatively large clocks. Right-click the clocks to choose what you want them to display:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Grid: regions must start on the nearest grid point"
+msgid "<guimenuitem>Bars:Beats</guimenuitem> displays the number of bars and beats"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Magnetic: regions can move freely, but when they are near a grid point, they will automatically 'snap' to it"
+msgid "<guimenuitem>Minutes:Seconds</guimenuitem> displays the time since beginning of track"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "middle menu: (how to place the grid-lines)"
+msgid "<guimenuitem>Timecode</guimenuitem> displays frames-per-second timecode (usually for work with films)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "SMPTE things: for timecode"
+msgid "<guimenuitem>Samples</guimenuitem> displays the samples since start"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "seconds and minutes: for time"
+msgid "If you do not need both clocks, you can turn one of them off."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "beats and bars: for that"
+msgid "The <guimenu>snap mode</guimenu> menu is located between the timeline and the clocks. This menu controls where regions may move. You need to change these as you work with a session, depending on the current activity. The left menu contains:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Region stuff: edges of regions"
+msgid "<guimenuitem>No Grid</guimenuitem>: regions can move freely"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Explain the thing to the right, which allows you to move the playhead by certain amounts."
+msgid "<guimenuitem>Grid</guimenuitem>: regions must start on the nearest grid point"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The timeline (which contains many \"rulers\" showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars."
+msgid "<guimenuitem>Magnetic</guimenuitem> regions can move freely, but when they are near a grid point, they automatically snap to it"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the right-click menu to select which rulers you want to display."
+msgid "The middle menu controls where to place the grid lines; by timecode, by clock time, by beats and bars, or by regions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The rulers you should choose depends on the clock settings and the snap mode."
+msgid "The timeline (which contains many <firstterm>rulers</firstterm> showing different time-marking scales) is located at the top of the canvas area, underneath the toolbars. Use the right-click menu to select which rulers you want to display. The rulers you should choose depends on the clock settings and the snap mode."
msgstr ""
#. Tag: title
@@ -240,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>"
+msgid "The name of the track onto which you want to record should be the name of the input in <systemitem>JACK</systemitem>."
msgstr ""
#. Tag: title
@@ -250,72 +325,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is what a bus is. By default there's a master bus, to which will be sent everything you're going to export. Busses don't contain regions. A bus is like a \"batch collecting zone,\" so for example you send all the audio-to-be-exported to the master bus, where you can subject the whole project to a particular filter or volume-adjustment."
+msgid "Refer to <xref linkend=\"sect-Musicians_Guide-Vocabulary-Bus\" /> for a general discussion of busses. By default, everything that you export from <application>Ardour</application> is sent to a master bus. Busses do not contain regions but function as a batch collecting zone, where you can subject the whole project to a particular filter or volume adjustment."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Add a track for recording:"
+msgid "Add a track for recording"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Track > Add Track/Bus'"
+msgid "Click <menuchoice><guimenu>Track</guimenu><guimenuitem>Add Track/Bus</guimenuitem></menuchoice>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "ensure that \"Tracks\" is selected"
+msgid "ensure that <guilabel>Tracks</guilabel> is selected"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "set the number (probably 1)"
+msgid "set the number (probably <literal>1</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the number of input channels (probably \"Stereo\" meaning 2)"
+msgid "select the number of input channels (probably <literal>Stereo</literal>, meaning 2)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "select the mode"
+msgid "select the mode:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Normal\": creates a new Region for each recording \"take\""
+msgid "<literal>Normal</literal>: creates a new Region for each recording take"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "\"Tape\": will destructively record of whatever is already recorded (like a tape)"
+msgid "<literal>Tape</literal>: destructively records over whatever is already recorded (like a tape)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click 'Add' to create them"
+msgid "Click <guibutton>Add</guibutton> to create the track"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Rename the tracks, so that you know what's on them:"
+msgid "Rename tracks, to identify them"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "easiest way is click on the track name on the box-thing on the left side of the big area"
+msgid "Click the existing track name in the label to the far left of the track area"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "erase what's there and put in a better name"
+msgid "Type over the existing name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "when you're done, press \"enter\""
+msgid "press <keycap>Enter</keycap>"
msgstr ""
#. Tag: title
@@ -325,12 +400,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unless you're just learning or doing quick, personal-use experimentation, it is important to properly set the level of the inputs betfore recording."
+msgid "It is important to properly set the level of the inputs betfore recording."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The nature of audio equipment (including our ears, I think?) is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about one's own ears, if a sound is far too loud, it may permanently damage the audio instrument."
+msgid "The nature of audio equipment is such that it can only perceive sound pressures (perceived as volume) within a certain range. If a sound is too quiet, it will not be perceived, and if it is too loud, it will not be perceived accurately. Furthermore, and this is most important when thinking about your own ears — if a sound is far too loud, it may permanently damage the audio instrument."
msgstr ""
#. Tag: para
@@ -340,7 +415,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to imagine how <application>Ardour</application> acts when it records silence. When <application>Ardour</application> thinks that a portion of audio is too loud, it outlines the wave-form representation in red, as shown in this image: <inlinemediaobject><imageobject> <imagedata fileref=\"./images/Ardour-red_peaks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "When <application>Ardour</application> records silence, it behaves no differently from when there is no input at all. When <application>Ardour</application> calculates that a portion of audio is too loud and therefore distorted, it outlines the wave-form representation in red, as shown in <xref linkend=\"ardour_red_peaks\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Audio that is too loud"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A waveform in Ardour, showing red peaks where the audio is too loud."
msgstr ""
#. Tag: para
@@ -355,7 +440,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Route the microphone through a mixer before it hits the audio interface"
+msgid "Route the microphone through a mixer before it reaches the audio interface"
msgstr ""
#. Tag: para
@@ -365,7 +450,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here are the pros and cons of each approach."
+msgid "Here are the advantages and disadvantages of each approach:"
msgstr ""
#. Tag: para
@@ -500,7 +585,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
+msgid "if there is nothing to the left of the editor window, press Ctrl+E or 'View > Show Editor Mixer'"
msgstr ""
#. Tag: para
@@ -970,7 +1055,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Track > Add Track/Bus'"
+msgid "From the menu, select 'Track > Add Track/Bus'"
msgstr ""
#. Tag: para
@@ -1180,7 +1265,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
+msgid "If you can't see the editor mixer, open it by using the menu. Click 'View > Show Editor Mixer' so that it is checked. You can also press 'Shift + E' on the keyboard to toggle its display."
msgstr ""
#. Tag: para
@@ -1333,19 +1418,9 @@ msgstr ""
msgid "Verify that only the five busses are connected to the master bus' inputs."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Ardour-Connections.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
-msgstr ""
-
#. Tag: title
#, no-c-format
-msgid "Creating Edit Groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Explain how to do that, and why."
+msgid "Connections in Ardour"
msgstr ""
#. Tag: title
@@ -2005,7 +2080,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
+msgid "Notice that <application>Ardour</application> puts > and < around the name of the region, in the canvas area."
msgstr ""
#. Tag: para
@@ -2340,7 +2415,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
+msgid "Open the mixer window by selecting from the menu 'Window > Show Mixer'. If you have a multiple-monitor setup, it can be very useful to keep the mixer window on a separate monitor from the main editor window. If you don't have a multiple-monitor setup, you can keep the mixer window on a separate virtual desktop. Of course, these are both optional steps."
msgstr ""
#. Tag: para
@@ -2385,7 +2460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
+msgid "Open the mixer window with the menu, by choosing 'Window > Mixer'. As mentioned earlier, it can be convenient to put the mixer window on another monitor or virtual desktop."
msgstr ""
#. Tag: para
@@ -2770,7 +2845,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
+msgid "From the menu, select 'Session > Export > Export > Export session to audiofile', or on the keyboard, press 'Ctrl + Alt + e'"
msgstr ""
#. Tag: title
diff --git a/zh-TW/Audacity.po b/zh-TW/Audacity.po
index cb97802..0e4ae65 100644
--- a/zh-TW/Audacity.po
+++ b/zh-TW/Audacity.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,7 +25,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Kowing When to Use Audacity"
+msgid "Knowing When to Use Audacity"
msgstr ""
#. Tag: para
@@ -90,7 +90,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use PackageKit or KPackageKit to install the <code>audacity</code> package."
+msgid "Use PackageKit or KPackageKit to install the <package>audacity</package> package."
msgstr ""
#. Tag: para
@@ -115,7 +115,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run this command in a terminal: <command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgid "Run this command in a terminal:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/\\</command>\n"
+"<command>rpmfusion-free-release-stable.noarch.rpmhttp://download1.rpmfusion.org/nonfree/\\</command>\n"
+"<command>fedora/rpmfusion-nonfree-release-stable.noarch.rpm'</command>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this a single command, broken into three lines here for presentation reasons."
msgstr ""
#. Tag: para
@@ -280,16 +293,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <code>cat</code> program outputs a list of sound cards in your computer, which looks similar to this list:"
+msgid "The <command>cat</command> program outputs a list of sound cards in your computer, which looks similar to this list:"
msgstr ""
-#. Tag: literallayout
+#. Tag: screen
#, no-c-format
msgid ""
-"0 [SB ]: HDA-Intel - HDA ATI SB\n"
-" HDA ATI SB at 0xf7ff4000 irq 16\n"
-"1 [MobilePre ]: USB-Audio - MobilePre\n"
-" M Audio MobilePre at usb-0000:00:13.0-2"
+"<computeroutput>0 [SB ]: HDA-Intel - HDA ATI SB</computeroutput>\n"
+"<computeroutput> HDA ATI SB at 0xf7ff4000 irq 16</computeroutput>\n"
+"<computeroutput>1 [MobilePre ]: USB-Audio - MobilePre</computeroutput>\n"
+"<computeroutput> M Audio MobilePre at usb-0000:00:13.0-2</computeroutput>"
msgstr ""
#. Tag: para
@@ -304,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
+msgid "Open the \"Preferences\" window. Choose <guimenu>File</guimenu> > <guimenuitem>Preferences</guimenuitem>."
msgstr ""
#. Tag: para
@@ -357,9 +370,59 @@ msgstr ""
msgid "The Interface"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Audacity interface"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An Audacity window, displaying a single stereo track."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>transport controls</firstterm> play, stop, or pause playback of audio. The buttons to record and move quickly through a file are also located here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>tool-selection box</firstterm> changes the cursor's function."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The two <firstterm>volume level meters</firstterm> display the volume level of stereo audio. The left meter displays the volume level of the output signal. The right meter displays the volume level of the input signal."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>ruler</firstterm> displays the time since the start of the file, in minutes and seconds."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each <firstterm>track</firstterm> contains two channels of audio signal data. Audacity stacks tracks vertically in the main window. Audacity plays back all tracks simultaneously."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A track in Audacity"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A single stereo track, displayed in Audacity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Each track has a <firstterm>track info area</firstterm>, which holds settings like the fader, panner, and <guibutton>mute</guibutton> and <guibutton>solo</guibutton> buttons."
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-Audacity-Interface.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>timeline</firstterm> is the main area of the main window of Audacity. The leftmost point is the beginning of the audio file."
msgstr ""
#. Tag: para
diff --git a/zh-TW/Audio_Vocabulary.po b/zh-TW/Audio_Vocabulary.po
index 7d631ba..b9a7757 100644
--- a/zh-TW/Audio_Vocabulary.po
+++ b/zh-TW/Audio_Vocabulary.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -40,12 +40,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-master_sub_bus.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How audio busses work"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An <firstterm>audio bus</firstterm> sends audio signals from one place to another. Many different signals can be inputted to a bus simultaneously, and many different devices or applications can read from a bus simultaneously. Signals inputted to a bus are mixed together, and cannot be separated after entering a bus. All devices or applications reading from a bus receive the same signal."
+msgid "An example audio bus combining three signals. The combined output is sent to two separate devices or applications."
msgstr ""
#. Tag: para
@@ -58,6 +63,16 @@ msgstr ""
msgid "A <firstterm>sub-master bus</firstterm> combines audio signals before they reach the master bus. Using a sub-master bus is optional. They allow you to adjust more than one track in the same way, without affecting all the tracks."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The relationship between the master bus and sub-master busses"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two example sub-master busses, each combining two different signals and sending them to a master bus. The master bus combines the two signals into one signal that contains all four original signals."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Audio busses are also used to send audio into effects processors."
@@ -133,6 +148,16 @@ msgstr ""
msgid "<firstterm>Panning</firstterm> adjusts the portion of a channel's signal that is sent to each output channel. In a stereophonic (two-channel) setup, the two channels represent the \"left\" and the \"right\" speakers. Two channels of recorded audio are available in the DAW, and the default setup sends all of the \"left\" recorded channel to the \"left\" output channel, and all of the \"right\" recorded channel to the \"right\" output channel. Panning sends some of the left recorded channel's level to the right output channel, or some of the right recorded channel's level to the left output channel. Each recorded channel has a constant total output level, which is divided between the two output channels."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Panning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The left and right recorded channels being sent to the left output channel; the left recorded channel being sent to the left output channel and the right recorded channel being sent to the right output channel, and the left and right recorded channels being sent to the right output channel."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "The default setup for a left recorded channel is for \"full left\" panning, meaning that 100% of the output level is output to the left output channel. An audio engineer might adjust this so that 80% of the recorded channel's level is output to the left output channel, and 20% of the level is output to the right output channel. An audio engineer might make the left recorded channel sound like it is in front of the listener by setting the panner to \"center,\" meaning that 50% of the output level is output to both the left and right output channels."
@@ -143,6 +168,16 @@ msgstr ""
msgid "Balance is sometimes confused with panning, even on commercially-available audio equipment. Adjusting the <firstterm>balance</firstterm> changes the volume level of the output channels, without redirecting the recorded signal. The default setting for balance is \"center,\" meaning 0% change to the volume level. As you adjust the dial from \"center\" toward the \"full left\" setting, the volume level of the right output channel is decreased, and the volume level of the left output channel remains constant. As you adjust the dial from \"center\" toward the \"full right\" setting, the volume level of the left output channel is decreased, and the volume level of the right output channel remains constant. If you set the dial to \"20% left,\" the audio equipment would reduce the volume level of the right output channel by 20%, increasing the perceived loudness of the left output channel by approximately 20%."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Balance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The right output channel silenced (balance full left), the left and right channels at equal volume (balance centered), the left output channel silenced (balance full right)."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "You should adjust the balance so that you perceive both speakers as equally loud. Balance compensates for poorly set up listening environments, where the speakers are not equal distances from the listener. If the left speaker is closer to you than the right speaker, you can adjust the balance to the right, which decreases the volume level of the left speaker. This is not an ideal solution, but sometimes it is impossible or impractical to set up your speakers correctly. You should adjust the balance only at final playback."
@@ -205,7 +240,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/FMG-routing_and_multiplexing.png\" format=\"PNG\" /> </imageobject></inlinemediaobject> <firstterm>Routing</firstterm> audio transmits a signal from one place to another - between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgid "<firstterm>Routing</firstterm> audio transmits a signal from one place to another — between applications, between parts of applications, or between devices. On Linux systems, the <systemitem>JACK Audio Connection Kit</systemitem> is used for audio routing. <systemitem>JACK</systemitem>-aware applications (and <systemitem>PulseAudio</systemitem> ones, if so configured) provide inputs and outputs to the <systemitem>JACK</systemitem> server, depending on their configuration. The <application>QjackCtl</application> application can adjust the default connections. You can easily reroute the output of a program like FluidSynth so that it can be recorded by <application>Ardour</application>, for example, by using <application>QjackCtl</application>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Routing and multiplexing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Illustration of routing and multiplexing in the <guilabel>Connections</guilabel> window of the <application>QjackCtl</application> interface."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus inputs accept multiplexed audio from many sources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Master bus outputs routed to system playback inputs."
msgstr ""
#. Tag: para
diff --git a/zh-TW/Digital_Audio_Workstations.po b/zh-TW/Digital_Audio_Workstations.po
index 83d07de..11e5e94 100644
--- a/zh-TW/Digital_Audio_Workstations.po
+++ b/zh-TW/Digital_Audio_Workstations.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -210,6 +210,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A session in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A session in Ardour, containing multiple instrumental tracks."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Track and Multitrack"
msgstr ""
@@ -220,6 +230,16 @@ msgstr ""
#. Tag: title
#, no-c-format
+msgid "A track in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A track in Ardour, containing a single region amid a period of silence during which this instrument is not heard."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
msgid "Region, Clip, or Segment"
msgstr ""
@@ -250,7 +270,12 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Relationship of Session, Track, and Region"
+msgid "A region in Ardour"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A region in Ardour."
msgstr ""
#. Tag: title
@@ -290,17 +315,22 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Messages\" Pane"
+msgid "Messages Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor messages pane"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-messages.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The messages pane at the bottom of the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"messages\" pane, shown in the above diagram, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the \"messages\" pane for information that may help you to get the desired results. The \"messages\" pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
+msgid "The <guilabel>messages</guilabel> pane, shown in <xref linkend=\"qtractor_messages\" />, contains messages produced by the DAW, and sometimes messages produced by software used by the DAW, such as <systemitem>JACK</systemitem>. If an error occurs, or if the DAW does not perform as expected, you should check the <guilabel>messages</guilabel> pane for information that may help you to get the desired results. The <guilabel>messages</guilabel> pane can also be used to determine whether <systemitem>JACK</systemitem> and the DAW were started successfully, with the options you prefer."
msgstr ""
#. Tag: title
@@ -308,64 +338,109 @@ msgstr ""
msgid "Clock"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor clock"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-clocks.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The clock in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The clock shows the current place in the file, as indicated by the transport. In the image, you can see that the transport is at the beginning of the session, so the clock indicates \"0\". This clock is configured to show time in minutes and seconds, so it is a \"time clock.\" Other possible settings for clocks are to show BBT (bars, beats, and ticks - a \"MIDI clock\"), samples (a \"sample clock\"), or an SMPTE timecode (used for high-precision synchronization, usually with video - a \"timecode clock\"). Some DAWs allow the use of multiple clocks simultaneously."
+msgid "The clock shows the current place in the file, as indicated by the transport. In <xref linkend=\"qtractor_clocks\" />, you can see that the transport is at the beginning of the session, so the clock indicates <literal>0</literal>. This clock is configured to show time in minutes and seconds, so it is a <firstterm>time clock</firstterm>. Other possible settings for clocks are to show <firstterm>BBT</firstterm> (bars, beats, and ticks — a <firstterm>MIDI clock</firstterm>), samples (a <firstterm>sample clock</firstterm>), or an <firstterm>SMPTE timecode</firstterm> (used for high-precision synchronization, usually with video — a <firstterm>timecode clock</firstterm>). Some DAWs allow the use of multiple clocks simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that this particular time clock in \"Qtractor\" also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
+msgid "Note that this particular time clock in <application>Qtractor</application> also offers information about the MIDI tempo and metre (120.0 beats per minute, and 4/4 metre), along with a quantization setting for MIDI recording."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track Info\" Pane"
+msgid "Track Info Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track info pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track info pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track_info.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The track info pane: note a separate track info space for each of the two tracks that appear in the pane to the right."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown on this image: \"R\" for \"arm to record,\" \"M\" for \"mute/silence track's output,\" and \"S\" for \"solo mode,\" where only the selected tracks and busses are heard."
+msgid "The <firstterm>track info</firstterm> pane contains information and settings for each track and bus in the session. Here, you can usually adjust settings like the routing of a track's or bus' input and output routing, the instrument, bank, program, and channel of MIDI tracks, and the three buttons shown in <xref linkend=\"qtractor_track_info\" />: <guibutton>R</guibutton> for \"arm to record,\" <guibutton>M</guibutton> for \"mute/silence track's output,\" and <guibutton>S</guibutton> for \"solo mode,\" where only the selected tracks and busses are heard."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in \"track\" pane."
+msgid "The information provided, and the layout of buttons, can change dramatically between DAWs, but they all offer the same basic functionality. Often, right-clicking on a track info box will give access to extended configuration options. Left-clicking on a portion of the track info box that is not a button allows you to select a track without selecting a particular moment in <firstterm>track pane</firstterm>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track info\" pane does not scroll out of view as the \"track\" pane is adjusted, but is independent."
+msgid "The track info pane does not scroll out of view as the track pane is adjusted, but is independent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "\"Track\" Pane"
+msgid "Track Pane"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor track pane"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The track pane in the Qtractor window."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-track.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "The <firstterm>ruler</firstterm>, set here to <firstterm>BBT</firstterm> (bars, beats, ticks)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The \"track\" pane is the main workspace in a DAW. It shows regions (also called \"clips\") with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The \"track\" pane shows the transport as a vertical line; in this image it is the left-most red line in the \"track\" pane."
+msgid "Two tracks, presented as graphical representations. The horizontal axis repesents time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Scrolling the \"track\" pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the \"track\" pane allows you to view the regions and tracks in a particular time range."
+msgid "A MIDI <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "An audio <firstterm>clip</firstterm> (known as a <firstterm>region</firstterm> in other applications)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrollbar for the track pane; note that this pane scrolls independently."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <firstterm>track pane</firstterm> is the main workspace in a DAW. It shows <firstterm>regions</firstterm> (also called <firstterm>clips</firstterm>) with a rough overview of the audio wave-form or MIDI notes, allows you to adjust the starting-time and length of regions, and also allows you to assign or re-assign a region to a track. The track pane shows the transport as a vertical line; in <xref linkend=\"qtractor_track\" /> it is the left-most red line in the track pane."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Scrolling the track pane horizontally allows you to view the regions throughout the session. The left-most point is the start of the session; the right-most point is after the end of the session. Most DAWs allow you to scroll well beyond the end of the session. Scrolling vertically in the track pane allows you to view the regions and tracks in a particular time range."
msgstr ""
#. Tag: title
@@ -373,9 +448,44 @@ msgstr ""
msgid "Transport Controls"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "The Qtractor transport controls"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transport controls in the Qtractor window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to beginning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast reverse"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport fast forward"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport skip to end"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Transport forward at real time"
+msgstr ""
+
#. Tag: para
#, no-c-format
-msgid "<inlinemediaobject><imageobject> <imagedata fileref=\"./images/Qtractor-interface-transport.png\" format=\"PNG\" /> </imageobject></inlinemediaobject>"
+msgid "Arm for recording"
msgstr ""
#. Tag: para
@@ -385,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the beginning of the session."
+msgid "The single, left-pointing arrow with a vertical line will move the transport to the start of the session, without playing or recording any material. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the start of the session, the transport will skip to the blue place-marker. Press the button again to the next blue place-marker or the beginning of the session."
msgstr ""
#. Tag: para
@@ -395,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. You can press the button again if you wish to skip to the next blue place-marker or the end of the last region in the session."
+msgid "The single, right-pointing arrow with a vertical line will move the transport to the end of the last region currently in a session. In <application>Qtractor</application>, if there is a blue place-marker between the transport and the end of the last region in the session, the transport will skip to the blue place-marker. Press the button again to skip to the next blue place-marker or the end of the last region in the session."
msgstr ""
#. Tag: para
@@ -405,5 +515,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's \"arm\" button only turns red if a track is armed."
+msgid "The circular button arms the transport for recording. It is conventionally red in colour. In <application>Qtractor</application>, the transport can only be armed <emphasis>after</emphasis> at least one track has been armed; to show this, the transport's arm button only turns red if a track is armed."
msgstr ""
diff --git a/zh-TW/LilyPond/LilyPond-counterpoint.po b/zh-TW/LilyPond/LilyPond-counterpoint.po
index 1b80644..e127613 100644
--- a/zh-TW/LilyPond/LilyPond-counterpoint.po
+++ b/zh-TW/LilyPond/LilyPond-counterpoint.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -55,7 +55,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Use the 'LilyPond > Setup New Score' dialogue"
+msgid "Use the 'LilyPond > Setup New Score' dialogue"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
+msgid "You have to put each interval between < > brackets. The note-length of the figure's duration goes after the >, so I end up with \"<1>1 <3> <5> <4> <3> <3> <5> <5> <5> <5> <3> <1>\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
+msgid "I've ended up with a lower part that is \"f1 e d a bes c d e f d c f\", which gives figures that are \"<1>1 <3> <5> <6> <3> <3> <3> <6> <3> <3> <5> <1>\""
msgstr ""
#. Tag: title
@@ -320,7 +320,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
+msgid "But even this isn't quite right. You want a double-barline at the end. So, put the cursor after the \\revert lines, and then from the menu, 'LilyPond > Bar Lines > Ending Bar Line' . It knows what you want, remembers the symbol for you, so you don't have to!"
msgstr ""
#. Tag: para
diff --git a/zh-TW/LilyPond/LilyPond-orchestra.po b/zh-TW/LilyPond/LilyPond-orchestra.po
index 9fda4fb..c563831 100644
--- a/zh-TW/LilyPond/LilyPond-orchestra.po
+++ b/zh-TW/LilyPond/LilyPond-orchestra.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -60,7 +60,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'LilyPond > Setup New Score'"
+msgid "'LilyPond > Setup New Score'"
msgstr ""
#. Tag: para
@@ -262,52 +262,52 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Flute --> Flauto"
+msgid "Flute --> Flauto"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe I --> I Oboe"
+msgid "Oboe I --> I Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Oboe II --> II Oboe"
+msgid "Oboe II --> II Oboe"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bassoon --> 2 Fagotti"
+msgid "Bassoon --> 2 Fagotti"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
+msgid "Horn in F --> 2 Corni in Sol (NB: these would have been \"natural horns\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
+msgid "Trumpet in C --> 2 Clarini in Do (NB: a clarino is a kind of trumpet)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin I --> Violino I"
+msgid "Violin I --> Violino I"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Violin II --> Violino II"
+msgid "Violin II --> Violino II"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cello --> Violoncello obligato"
+msgid "Cello --> Violoncello obligato"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Contrabass --> Basso"
+msgid "Contrabass --> Basso"
msgstr ""
#. Tag: para
@@ -601,7 +601,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
+msgid "The other issue with the horn part is that two pitches are to be played at once, and they are both notated in the same voice. This is solved in the piano example like this: <code><g g'></code>. You can copy-and-paste this as needed."
msgstr ""
#. Tag: para
@@ -666,12 +666,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
+msgid "Anything between <literal><<</literal> and <literal>>></literal> is interpreted by LilyPond as happening together. If you take a look at the \"score\" section at the bottom of the file, you will see that all of the parts are listed in that kind of bracket. This ensures that they all happen simultaneously."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
+msgid "For short-term polyphonic input, use the formula <code><< { upper-voice notes } \\\\ { lower-voice notes } >></code>. Remember that the \"upper voice\" has upward-pointing stems, and the \"lower voice\" has downward-pointing stems."
msgstr ""
#. Tag: para
@@ -691,12 +691,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
+msgid "These are added like other dynamic markings, attached with a backslash to the note where they begin. A crescendo is triggered with <literal>\\<</literal> and a diminuendo with <literal>\\></literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
+msgid "The left-most point of the marking (its beginning) is indicated by where you put <literal>\\<</literal> or <literal>\\></literal>"
msgstr ""
#. Tag: para
@@ -736,7 +736,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
+msgid "The code needed for this is a little bit complicated, but you don't need to write it yourself: just take it from the \"tempoMark\" section created by Frescobaldi. All you need to do is change \"Adagio\" to \"Allegro spiritoso,\" and add the barline indicator. This is also easy because of Frescobaldi: 'LilyPond > Bar Lines > Repeat start'"
msgstr ""
#. Tag: para
diff --git a/zh-TW/LilyPond/LilyPond-piano.po b/zh-TW/LilyPond/LilyPond-piano.po
index ad24b4b..fa4c904 100644
--- a/zh-TW/LilyPond/LilyPond-piano.po
+++ b/zh-TW/LilyPond/LilyPond-piano.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -65,7 +65,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
+msgid "Start the \"Setup New Score\" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu."
msgstr ""
#. Tag: para
@@ -331,12 +331,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is more common: <literal><as ces>4-_</literal> Notice how only the pitches are notated inside the <literal>< ></literal> brackets, and everything else attached to the end. There is one exception to this: fingering should be indicated on the pitch associated with that finger: <literal><as-1 ces-3>4-_</literal> Not only does this help you to sort out what was probably intended, but it allows <application>LilyPond</application> to stack the fingering in the right order. When using \"relative\" entry mode, it is the lowest note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
+msgid "This style of chord notation is less common: <literal><<as4-> ces>></literal> Notice how everything must be notated inside the <literal><< >></literal> brackets. This can make it more difficult to read the chord in the source file, but it also allows much greater flexibility: only some chord members can have ties; certain chord members can last for longer than others; certain chord members can \"break out\" into or out of polyphonic passages. This notation is rarely <emphasis>needed</emphasis>, but you may be inclined to over-use it if you are trying to exactly copy the look of a hand-engraved score. Like the \"times\" command for tuplets, this is one of <application>LilyPond</application>'s deceptively powerful techniques. When using \"relative\" entry mode, it is the last note of the chord that is taken into consideration when placing the next note."
msgstr ""
#. Tag: title
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
+msgid "When entering chords, it is recommended that you enter the fingering with the note to which it is attached, like <literal><as-1 ces-4>4-_</literal>. It is possible to enter this as <literal><as ces>4-1-4-></literal>, but this not only looks confusing, it may confuse <application>LilyPond</application> as to which digit is intended for which note."
msgstr ""
#. Tag: para
@@ -381,12 +381,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
+msgid "Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal>\\<</literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal>\\<</literal> to start and <code>\\!</code> to end explicitly). However, if you want to use text and a \"spanner\" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\\crescTextCresc</code>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
+msgid "After changing to this style of <foreignphrase>crescendo</foreignphrase>, you can revert to the standard < style with the following command: <literal>\\crescHairpin</literal>."
msgstr ""
#. Tag: para
@@ -401,7 +401,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
+msgid "Sometimes, especially in piano music, a passage of some measures will require polyphonic (multi-Voice) notation in <application>LilyPond</application>, even though most of the music does not. In this case, you would use the following format: <literal> << { % upper voice notes go here } \\\\ { % lower voice notes go here } >> </literal> This is used a few times in both hands in the example score file."
msgstr ""
#. Tag: para
@@ -528,14 +528,14 @@ msgid ""
" {\n"
" instrumentName = \"Piano\"\n"
" }\n"
-"<<\n"
+"<<\n"
" \n"
"ew Staff = \"right\" \\right\n"
" \n"
"ew PianoDynamics = \"dynamics\" \\dynamics\n"
" \n"
"ew Staff = \"left\" { \\clef bass \\left }\n"
-">>\n"
+">>\n"
msgstr ""
#. Tag: para
@@ -616,7 +616,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
+msgid "For example, if you want a <foreignphrase>piano</foreignphrase> marking on the first beat, and a <foreignphrase>diminuendo</foreignphrase> from the third to the fourth beat, you could write this: <code>s4\\p r s\\> s\\!</code>, or this: <code>s2\\p s4\\> s\\!</code>"
msgstr ""
#. Tag: para
diff --git a/zh-TW/LilyPond/LilyPond-syntax.po b/zh-TW/LilyPond/LilyPond-syntax.po
index 3c7b5dd..c84aace 100644
--- a/zh-TW/LilyPond/LilyPond-syntax.po
+++ b/zh-TW/LilyPond/LilyPond-syntax.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>></literal> for an \"accent\""
+msgid "<literal>></literal> for an \"accent\""
msgstr ""
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
+msgid "Simply put, anything enclosed inside <literal><<</literal> and <literal>>></literal> is considered by <application>LilyPond</application> to happen simultaneously. This can be used in any context (and any Context - see above/below). It is possible to tell <application>LilyPond</application> that you want two notes to happen at the same time in the same voice (yielding a chord), at the same time on the same staff (yielding polyphony), and so on. Moreover, any score with multiple staves will use <literal><<</literal> and <literal>>></literal> to tell <application>LilyPond</application> that the parts should begin at the same time, and creative use of <literal><<</literal> and <literal>>></literal> is one of the keys to advanced notation."
msgstr ""
#. Tag: para
@@ -200,17 +200,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
+msgid "Making use of the <literal><<</literal> and <literal>>></literal> idea to indicate simultaneity, if a note has multiple pitches indicated between <literal>></literal> and <literal><</literal> then <application>LilyPond</application> assumes that they are in a chord together. Notating a single chord with single <literal>< ></literal> brackets has two advantages: firstly, it is easier to see that they are a chord and not something more complex; secondly, it allows you to enter information more clearly."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
+msgid "Consider the following examples, which should produce equivalent output: <code><<g'4->-5 b d>></code> and <code><g' b d>4->-5</code> With the first example, it is more difficult to see the chord notes, the duration, and what the <literal>5</literal> means. With the second example, it is easy to see that the chord notes are a <literal>G</literal>, a <literal>B</literal>, and a <literal>D</literal>, that they have quarter-note duration, and that the <literal>5</literal> is actually a fingering indication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
+msgid "There is another advantage to using <literal><</literal> and <literal>></literal> for notation of simple chords: they preserve logical continuity in \"relative\" mode. The following note will always be notated as relative to the lowest note in the chord, regardless of how many octaves the chord covers. This is not true with <literal><<</literal> and <literal>>></literal>, where where following notes will be notated as relative to the last note between the <literal><<</literal> and <literal>>></literal>"
msgstr ""
#. Tag: title
diff --git a/zh-TW/Planet_CCRMA_at_Home.po b/zh-TW/Planet_CCRMA_at_Home.po
index 31f881d..11f9a17 100644
--- a/zh-TW/Planet_CCRMA_at_Home.po
+++ b/zh-TW/Planet_CCRMA_at_Home.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,12 +150,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will have to use a terminal window for the next portion."
+msgid "Run the following command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"<command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/\\</command>\n"
+"<command>planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm</command>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the following commands: <command>su -c 'rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/13/i386/planetccrma-repo-1.1-2.fc13.ccrma.noarch.rpm'</command> This works for all versions of Fedora, whether 32-bit and 64-bit"
+msgid "This works for all versions of Fedora, whether 32-bit and 64-bit. Note that the command is a single line, broken here for presentation purposes."
msgstr ""
#. Tag: para
diff --git a/zh-TW/Qtractor.po b/zh-TW/Qtractor.po
index fdaa731..0a2210e 100644
--- a/zh-TW/Qtractor.po
+++ b/zh-TW/Qtractor.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:08\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
+msgid "Qtractor will work by itself, without further configuration. The options described here are for the settings you are most likely to want to discuss. Click on 'View > Options' to open the \"Options\" window."
msgstr ""
#. Tag: title
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'View > Instruments'"
+msgid "Click on 'View > Instruments'"
msgstr ""
#. Tag: para
@@ -495,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
+msgid "To view the JACK connections window within Qtractor, press the F8 key, or click 'View > Connections'. Pressing F8 again will hide the window. Qtractor's \"MIDI\" tab displays the devices on QjackCtl's \"ALSA\" tab."
msgstr ""
#. Tag: para
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
+msgid "Create a new audio track in Qtractor by clicking on 'Track > Add Track'."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
+msgid "Export the file as you normally would by clicking 'Track > Export Tracks > Audio'."
msgstr ""
#. Tag: para
@@ -590,7 +590,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
+msgid "You can choose whether or not you want the track pane to automatically scroll as the transport moves by clicking 'Transport > Follow Playhead'."
msgstr ""
#. Tag: title
@@ -626,7 +626,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
+msgid "You can import LilyPond's MIDI output by clicking 'Track > Import Tracks > MIDI' in Qtractor."
msgstr ""
#. Tag: title
@@ -801,7 +801,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Create a new clip by clicking on \"Edit > Clip > New\""
+msgid "Create a new clip by clicking on \"Edit > Clip > New\""
msgstr ""
#. Tag: para
@@ -901,7 +901,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Edit > Select > Select All'"
+msgid "Click on 'Edit > Select > Select All'"
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on 'Tools > Randomize'"
+msgid "Click on 'Tools > Randomize'"
msgstr ""
#. Tag: para
@@ -941,7 +941,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
+msgid "If you want to re-try the randomization, click on 'Edit > Undo Randomization', then use the \"Randomize\" tool again."
msgstr ""
#. Tag: para
@@ -991,12 +991,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
+msgid "Click on the first MIDI segment to select it, then copy it by clicking on 'Edit > Copy' or Control-c"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
+msgid "Paste it by clicking on 'Edit > Paste' or Control-v"
msgstr ""
#. Tag: para
diff --git a/zh-TW/Revision_History.po b/zh-TW/Revision_History.po
index 9bd6c4d..0c603fd 100644
--- a/zh-TW/Revision_History.po
+++ b/zh-TW/Revision_History.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -70,12 +70,12 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Re-formatted ex-<pre> tags."
+msgid "Re-formatted ex-<pre> tags."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Changed images to <inlinemediaobject>, where appropriate."
+msgid "Changed images to <inlinemediaobject>, where appropriate."
msgstr ""
#. Tag: member
@@ -85,17 +85,17 @@ msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed <code> tags, all but Basic Programming in SC."
+msgid "Reviewed <code> tags, all but Basic Programming in SC."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
+msgid "Reviewed use of <code> tags in \"Basic Programming in SC\" chapter."
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
+msgid "Searched code for '' or ''' and replaced them with <emphasis> where appropriate."
msgstr ""
#. Tag: member
diff --git a/zh-TW/Rosegarden.po b/zh-TW/Rosegarden.po
index 7d601cd..ca7bdb9 100644
--- a/zh-TW/Rosegarden.po
+++ b/zh-TW/Rosegarden.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "'Edit > Preferences'"
+msgid "'Edit > Preferences'"
msgstr ""
#. Tag: para
@@ -256,12 +256,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
+msgid "This MIDI file can then be imported into <application>Rosegarden</application> by selecting from the menu 'File > Import > Import MIDI File'. Unfortunately, this will erase the current session, so it can be done only once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
+msgid "It is also possible to export MIDI tracks to LilyPond format, which can then be edited further or simply turned into a score. To do this, from the menu select 'File > Export > Export LilyPond File'. After you select a location to save the file, <application>Rosegarden</application> allows you to control some score settings while exporting. After exporting a LilyPond file, you should inspect it with Frescobaldi before relying on it to be correct - computers sometimes make mistakes!"
msgstr ""
#. Tag: title
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
+msgid "From the <application>Rosegarden</application> menu, select 'Edit > Preferences'. Click the \"MIDI\" tab, then the 'General' tab, then select \"Send all MIDI controllers at start of each playback\". This will ensure that the MIDI synthesizer (<application>FluidSynth</application> for this tutorial) uses the right patches."
msgstr ""
#. Tag: para
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
+msgid "Select the newly-created percussion segment, then from the menu select 'Edit > Copy'."
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
+msgid "Press 'Ctrl + v' or from the menu choose 'Edit > Paste' a few times, so that the percussion track fills up the same space as the bassline."
msgstr ""
#. Tag: title
@@ -476,17 +476,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Edit > Select Whole Staff'."
+msgid "From the menu select 'Edit > Select Whole Staff'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
+msgid "Then from the menu select 'Adjust > Notes > Eighth Note'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
+msgid "This compressed the notes, which isn't what you wanted. Undo the change with 'Edit > Undo'."
msgstr ""
#. Tag: para
@@ -496,7 +496,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
+msgid "From the menu select 'Adjust > Notes > Eighth Note (Without Duration Change)'."
msgstr ""
#. Tag: para
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
+msgid "Now the segment repeats forever. This can be useful, but eventually you'll want to stop the song. When you want to change the repeats into copies, from the menu select 'Segment > Turn Repeats Into Copies'."
msgstr ""
#. Tag: para
diff --git a/zh-TW/Solfege.po b/zh-TW/Solfege.po
index 673c88c..8110ddb 100644
--- a/zh-TW/Solfege.po
+++ b/zh-TW/Solfege.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
+msgid "These configuration options are not required, but you may wish to change them. They are all available from the \"Preferences\" window, accesible through Solfege's main menu: 'File > Preferences'."
msgstr ""
#. Tag: title
@@ -120,7 +120,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the menu, select 'File > Preferences'."
+msgid "From the menu, select 'File > Preferences'."
msgstr ""
#. Tag: para
diff --git a/zh-TW/Sound_Cards.po b/zh-TW/Sound_Cards.po
index ef404d8..9df6348 100644
--- a/zh-TW/Sound_Cards.po
+++ b/zh-TW/Sound_Cards.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:42\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:06:59\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -150,7 +150,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it. This diagram above illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
+msgid "The primary function of audio interfaces is to convert signals between analog and digital formats. As mentioned earlier, real sound has an infinite possibility of pitches, volumes, and durations. Computers cannot process infinite information, so the audio signal must be converted before they can use it."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A waveform approximated by computer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A smooth, continuous waveform approximated by discrete steps."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "source: <filename>pcm.svg</filename>, available from <ulink url=\"http://commons.wikimedia.org/wiki/File:Pcm.svg\" />"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram in <xref linkend=\"waveform\" /> illustrates the situation. The red wave shape represents a sound wave that could be produced by a singer or an acoustic instrument. The gradual change of the red wave cannot be processed by a computer, which must use an approximation, represented by the gray, shaded area of the diagram. This diagram is an exaggerated example, and it does not represent a real recording."
msgstr ""
#. Tag: para
diff --git a/zh-TW/SuperCollider/SuperCollider-Basic_Programming.po b/zh-TW/SuperCollider/SuperCollider-Basic_Programming.po
index 929434f..2475083 100644
--- a/zh-TW/SuperCollider/SuperCollider-Basic_Programming.po
+++ b/zh-TW/SuperCollider/SuperCollider-Basic_Programming.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -2183,7 +2183,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<"
+msgid "<"
msgstr ""
#. Tag: entry
@@ -2193,7 +2193,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "<="
+msgid "<="
msgstr ""
#. Tag: entry
@@ -2203,7 +2203,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">"
+msgid ">"
msgstr ""
#. Tag: entry
@@ -2213,7 +2213,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid ">="
+msgid ">="
msgstr ""
#. Tag: entry
@@ -2570,8 +2570,8 @@ msgstr ""
msgid ""
"\n"
"(\n"
-" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
-" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
+" var a = 5.isPositive && isNegative( 6 ) || 12 + 5 * 42 - 1 > 18 ;\n"
+" var b = ( 5.isPositive && isNegative( 6 ) ) || ( ((12 + 5) * 42 - 1) > 18 ); // parentheses help to clarify\n"
" \n"
" a && b; // evaluates to \"true\"\n"
")\n"
@@ -2861,10 +2861,10 @@ msgstr ""
msgid ""
"\n"
"case\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
-" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
+" <replaceable>booleanFunction</replaceable> <replaceable>resultFunction</replaceable>\n"
";\n"
msgstr ""
@@ -3846,8 +3846,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>variableHoldingSynth</replaceable>.free;\n"
-"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
+"<replaceable>variableHoldingSynth</replaceable>.free;\n"
+"<replaceable>variableHoldingSynth</replaceable> = nil;\n"
msgstr ""
#. Tag: para
@@ -4049,8 +4049,8 @@ msgstr ""
#, no-c-format
msgid ""
"\n"
-"<replaceable>myBusVariable</replaceable>.free;\n"
-"<replaceable>myBusVariable</replaceable> = nil;\n"
+"<replaceable>myBusVariable</replaceable>.free;\n"
+"<replaceable>myBusVariable</replaceable> = nil;\n"
msgstr ""
#. Tag: para
diff --git a/zh-TW/SuperCollider/SuperCollider.po b/zh-TW/SuperCollider/SuperCollider.po
index 4ac8c19..d6f9f0c 100644
--- a/zh-TW/SuperCollider/SuperCollider.po
+++ b/zh-TW/SuperCollider/SuperCollider.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-09-08T03:01:43\n"
+"POT-Creation-Date: 2010-11-02T04:33:09\n"
"PO-Revision-Date: 2010-09-07T21:07:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -413,7 +413,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
+msgid "You will probably also want to start a server at this point, so from the menu select '<application>SuperCollider</application> > Start Server'."
msgstr ""
#. Tag: para
@@ -457,12 +457,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
+msgid "Press 'Ctrl+E' on the keyboard, or from the menu select '<application>SuperCollider</application> > Evaluate'"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
+msgid "To stop all sound on the server, press 'Esc' on the keyboard, or from the menu select '<application>SuperCollider</application> > Stop Sound'"
msgstr ""
#. Tag: para
More information about the docs-commits
mailing list