Skip to content

GitLab

kdenlive
kdenlive
Commit 99db4be1 authored by Caulier Gilles's avatar Caulier Gilles
Browse files
Options

Add i18n docbook structure 

svn path=/trunk/kdenlive/; revision=251
parent a023e85e
Hide whitespace changes
Inline Side-by-side
Showing with 1031 additions and 1 deletion
doc/Makefile.am
View file @ 99db4be1
####### kdevelop will overwrite this part!!! (begin)##########
SUBDIRS = en
SUBDIRS = en fr
####### kdevelop will overwrite this part!!! (end)############
doc/en/Makefile.am
View file @ 99db4be1
......@@ -5,6 +5,15 @@ EXTRA_DIST = index.docbook
####### kdevelop will overwrite this part!!! (end)############
endocbook_DATA = index.docbook
endocbookdir = $(kde_htmldir)/en/kdenlive
KDE_LANG = en
KDE_DOCS = kdenlive
index_en.pot: index.docbook index-shifted.docbook
xml2pot index.docbook > index_en.pot
index-shifted.docbook: index.docbook
cat index.docbook | expand | sed s/^[\ ]*// > index-shifted.docbook
noinst_HEADERS = index_en.pot index-shifted.docbook
doc/fr/Makefile.am 0 → 100644
View file @ 99db4be1
EXTRA_DIST = index.docbook
KDE_LANG = fr
KDE_DOCS = kdenlive
docbook_DATA = index.docbook
docbookdir = $(kde_htmldir)/fr/kdenkive
index_fr.po: ../en/index_en.pot
msgmerge -o index_fr.po index_fr.po ../en/index_en.pot
index.docbook: ../en/index.docbook ../en/index_en.pot index_fr.po
${MAKE} index_fr.po ../en/index-shifted.docbook
@echo "converting french help"
@echo "(this takes very very long, please be patient...)"
po2xml ../en/index-shifted.docbook index_fr.po | \
sed s/^\<\!ENTITY\ %\ English\ /\<\!ENTITY\ %\ French\ /g > $@
noinst_HEADERS = index_fr.po
doc/fr/index.docbook 0 → 100644
View file @ 99db4be1
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kdenlive '<application
>Kdenlive</application
>'>
<!ENTITY kapp "&kdenlive;"
><!-- replace kdenlive here -->
<!ENTITY % addindex "IGNORE">
<!ENTITY % French "INCLUDE"
><!-- change language only here -->
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
]>
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
></title>
<authorgroup>
<author
> </author>
</authorgroup>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
<copyright>
<year
>2003</year>
<holder
></holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>28/07/2003</date>
<releaseinfo
>1.01.00</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
> </para>
<para
> </para>
<para
> </para>
<para
> </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
></keyword>
<keyword
></keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
></title>
<!-- The introduction chapter contains a brief introduction for the
application that explains what it does and where to report
problems. Basically a long version of the abstract. Don't include a
revision history. (see installation appendix comment) -->
<para
> </para>
<sect1 id="whatisavideoeditor">
<title
></title>
<para
> </para>
</sect1>
<sect1 id="linearvsnonlinear">
<title
></title>
<para
> </para>
<para
> </para>
</sect1>
</chapter>
<chapter id="using-kapp">
<title
></title>
<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->
<para
> <screenshot
> <screeninfo
></screeninfo
> <mediaobject
> <imageobject
> <imagedata fileref="screenshot.png" format="PNG"/> </imageobject
> <imageobject
> <imagedata fileref="screenshot.eps" format="EPS"/> </imageobject
> <textobject
> <phrase
></phrase
> </textobject
> </mediaobject
> </screenshot
> </para>
<sect1 id="kapp-projectlist">
<title
></title>
<para
> </para>
<para
> </para>
<sect2 id="kapp-projectlist-addingclips">
<title
></title>
<para
> </para>
<para
> </para>
</sect2>
<sect2 id="kapp-projectlist-deletingclips">
<title
></title>
<para
> </para>
</sect2>
<sect2 id="kapp-projectlist-clipproperties">
<title
></title>
<para
> </para>
</sect2>
<sect2 id="kapp-projectlist-cleanproject">
<title
></title>
<para
> </para>
</sect2>
</sect1>
<sect1 id="kapp-debugwindow">
<title
></title>
<para
></para>
</sect1>
<sect1 id="kapp-effectlist">
<title
></title>
<para
> </para>
</sect1>
<sect1 id="kapp-effectsetup">
<title
></title>
<para
> </para>
</sect1>
<sect1 id="kapp-timeline">
<title
></title>
<para
></para>
</sect1>
<sect1 id="kapp-clipmonitor">
<title
></title>
<para
></para>
</sect1>
<sect1 id="kapp-workspacemonitor">
<title
></title>
<para
></para>
</sect1>
<sect1 id="kapp-rendering">
<title
></title>
<para
></para>
</sect1>
<sect1 id="kapp-loadsave">
<title
></title>
<para
></para>
</sect1>
</chapter>
<chapter id="commands">
<title
></title>
<!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
application windows and their menubar and toolbar commands for easy reference.
Also include any keys that have a special function but have no equivalent in the
menus or toolbars. This may not be necessary for small apps or apps with no tool
or menu bars. -->
<sect1 id="kapp-mainwindow">
<title
></title>
<sect2>
<title
></title>
<para
> <variablelist
> <varlistentry
> <term
><menuchoice
> </menuchoice
></term
> <listitem
><para
><action
></action
></para
></listitem
> </varlistentry
> <varlistentry
> <term
><menuchoice
> </menuchoice
></term
> <listitem
><para
><action
></action
></para
></listitem
> </varlistentry
> <varlistentry
> <term
><menuchoice
> </menuchoice
></term
> <listitem
><para
></para
></listitem
> </varlistentry
> </variablelist
> </para>
</sect2>
</sect1>
</chapter>
<chapter id="developers">
<title
></title>
<!-- (OPTIONAL) A Programming/Scripting reference chapter should be
used for apps that use plugins or that provide their own scripting hooks
and/or development libraries. -->
<para
> </para>
<!-- Use refentries to describe APIs. Refentries are fairly complicated and you
should consult the docbook reference for further details. The example below was
taken from that reference and shortened a bit for readability. -->
</chapter>
<chapter id="faq">
<title
></title>
<!-- (OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work. -->
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
></para>
</question>
<answer>
<para
> </para>
</answer>
</qandaentry>
</qandaset>
</chapter>
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
></title>
<para
> </para>
<para
> </para>
<para
> <itemizedlist
> <listitem
> <para
> </para
> </listitem
> <listitem
> <para
> </para
> </listitem
> </itemizedlist
> </para>
<para
> </para>
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
&underFDL; <!-- FDL: do not remove. Commercial development should -->
<!-- replace this with their copyright and either remove it or re-set this.-->
<!-- Determine which license your application is licensed under,
and delete all the remaining licenses below:
(NOTE: All documentation are licensed under the FDL,
regardless of what license the application uses) -->
&underGPL; <!-- GPL License -->
</chapter>
<appendix id="installation">
<title
></title>
<sect1 id="getting-kdenlive">
<title
></title>
<para
> </para>
</sect1>
<sect1 id="requirements">
<title
></title>
<!--
List any special requirements for your application here. This should include:
.Libraries or other software that is not included in kdesupport,
kdelibs, or kdebase.
.Hardware requirements like amount of RAM, disk space, graphics card
capabilities, screen resolution, special expansion cards, etc.
.Operating systems the app will run on. If your app is designed only for a
specific OS, (you wrote a graphical LILO configurator for example) put this
information here.
-->
<para
> </para>
<para
> </para>
<!-- For a list of updates, you may refer to the application web site
or the ChangeLog file, or ... -->
<para
> </para>
</sect1>
<sect1 id="compilation">
<title
></title>
<para
> <screen width="40">
</screen
> </para>
<para
> </para>
</sect1>
<sect1 id="configuration">
<title
></title>
<para
> </para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->
doc/fr/index_fr.po 0 → 100644
View file @ 99db4be1
#: index.docbook:44
#, no-c-format
msgid "The Kdenlive Handbook"
msgstr ""
#: index.docbook:47
#, no-c-format
msgid ""
"<firstname>Jason</firstname> <othername>M.</othername> <surname>Wood</"
"surname> <affiliation> <address><email>jasonwood@blueyonder.co.uk</email></"
"address> </affiliation>"
msgstr ""
#: index.docbook:57
#, no-c-format
msgid "ROLES_OF_TRANSLATORS"
msgstr ""
#: index.docbook:61
#, no-c-format
msgid "Jason Wood"
msgstr ""
#: index.docbook:81
#, no-c-format
msgid "&kdenlive; is a non-linear video editor for KDE."
msgstr ""
#: index.docbook:84
#, no-c-format
msgid ""
"WARNING - this document has not yet been finished. In particular, "
"information on contributors to &kapp;, requirements for &kapp;, installation "
"instructions for &kapp; and the changelog info are all wrong at present. "
"Also, please contact me at <email>jasonwood@blueyonder.co.uk</email> rather "
"than bugging any of the kde mailing lists."
msgstr ""
#: index.docbook:90
#, no-c-format
msgid "Cheers,"
msgstr ""
#: index.docbook:93
#, no-c-format
msgid "Jason"
msgstr ""
#: index.docbook:103
#, no-c-format
msgid "<keyword>KDE</keyword>"
msgstr ""
#: index.docbook:104
#, no-c-format
msgid "video editor"
msgstr ""
#: index.docbook:105
#, no-c-format
msgid "kdenlive"
msgstr ""
#: index.docbook:120
#, no-c-format
msgid "Introduction"
msgstr ""
#: index.docbook:127
#, no-c-format
msgid ""
"&kapp; is a non-linear video editor for KDE. Please report any problems or "
"feature requests to jasonwood@blueyonder.co.uk"
msgstr ""
#: index.docbook:133
#, no-c-format
msgid "What is a video editor?"
msgstr ""
#: index.docbook:135
#, no-c-format
msgid ""
"A video editor is an application that allows you to create a new video out "
"of various scenes from one or more other videos."
msgstr ""
#: index.docbook:141
#, no-c-format
msgid "What is the difference between linear editing and non-linear editing?"
msgstr ""
#: index.docbook:143
#, no-c-format
msgid ""
"Before editing video on computer was possible, most editing was done on "
"linear editors - these work by having essentially, two video recorders. The "
"first would hold the video that you are editing together, and the second "
"would be used to find the next clip that you want to record. Find a clip, "
"record it, find the next clip, record it. This is called linear editing "
"because the medium of tape forced things to be edited sequentially. If you "
"have edited 10 minutes worth of footage together, and decide that you made a "
"mistake after five minutes, you can't just \"push\" the last five minutes "
"around to add space for new clips."
msgstr ""
#: index.docbook:154
#, no-c-format
msgid ""
"Non-linear editing is by far a more flexible way of editing. You can place "
"clips anywhere within your final video (in Kdenlive, this is represented via "
"the timeline), and you can move them around as much as you want, rearrange "
"them in a completely different order. Best of all, at any point during this "
"you can press play and (with a sufficiently powerful computer) watch back "
"what you have done there and then."
msgstr ""
#: index.docbook:165