Submitting the New TranslationPrepare the new translation files for submission. This
- example shows a new Spanish translation of the NanoBSD
- article in
- ~/doc/es_ES.ISO8859-1/articles/nanobsd.
+ includes adding the files to the version control system, setting
+ additional properties on them, then creating a diff for
+ submission.
+
+ The diff files created by these examples can be attached to
+ a documentation
+ bug report or code
+ review.
+
+
+ Spanish Translation of the NanoBSD Article
- The PO file must contain a &os;
- version string comment on the first line:
+ Add a &os; version string comment as the first
+ line of the PO file:#$FreeBSD$
- The Makefile, the
+ Add the Makefile, the
PO file, and the generated
- XML translation must all be added to
+ XML translation to
version control:&prompt.user; cd ~/doc/es_ES.ISO8859-1/articles/nanobsd/
@@ -821,9 +831,9 @@ A es_ES.po
- These files must also have the
+ Set the
Subversion
- svn:keywords property set to
+ svn:keywords properties on these files to
FreeBSD=%H so
$FreeBSD$ strings are expanded into
the path, revision, date, and author when committed:
@@ -835,21 +845,96 @@ property 'svn:keywords' set on 'es_ES.po'
- A diff of these new files is created from the
+ Set the MIME types of the files.
+ These are text/xml for books and
+ articles, and text/x-gettext-translation
+ for the PO file.
+
+ &prompt.user; svn propset svn:mime-type text/x-gettext-translation es_ES.po
+property 'svn:mime-type' set on 'es_ES.po'
+&prompt.user; svn propset svn:mime-type text/xml article.xml
+property 'svn:mime-type' set on 'article.xml'
+
+
+
+ Create a diff of the new files from the
~/doc/ base directory so the full path
is shown with the filenames. This helps committers identify
the target language directory.&prompt.user; cd ~/docsvn diff es_ES.ISO8859-1/articles/nanobsd/ > /tmp/es_nanobsd.diff
-
- The diff file is now ready for attachment to a
- documentation
- bug report or code
- review.
+
+
+
+ Korean UTF-8 Translation of the
+ Explaining-BSD Article
+
+
+
+ Add a &os; version string comment as the first
+ line of the PO file:
+
+ #$FreeBSD$
+
+
+
+ Add the Makefile, the
+ PO file, and the generated
+ XML translation to
+ version control:
+
+ &prompt.user; cd ~/doc/ko_KR.UTF-8/articles/explaining-bsd/
+&prompt.user; ls
+Makefile article.xml ko_KR.po
+&prompt.user; svn add Makefile article.xml ko_KR.po
+A Makefile
+A article.xml
+A ko_KR.po
+
+
+
+ Set the Subversion
+ svn:keywords properties on these files
+ to FreeBSD=%H so
+ $FreeBSD$ strings are
+ expanded into the path, revision, date, and author when
+ committed:
+
+ &prompt.user; svn propset svn:keywords FreeBSD=%H Makefile article.xml ko_KR.po
+property 'svn:keywords' set on 'Makefile'
+property 'svn:keywords' set on 'article.xml'
+property 'svn:keywords' set on 'ko_KR.po'
+
+
+
+ Set the MIME types of the files.
+ Because these files use the UTF-8
+ character set, that is also specified. To prevent the
+ version control system from mistaking these files for
+ binary data, the fbsd:notbinary
+ property is also set:
+
+ &prompt.user; svn propset svn:mime-type 'text/x-gettext-translation; charset=UTF-8' ko_KR.po
+property 'svn:mime-type' set on 'ko_KR.po'
+&prompt.user; svn propset fbsd:notbinary yes ko_KR.po
+property 'fbsd:notbinary' set on 'ko_KR.po'
+&prompt.user; svn propset svn:mime-type 'text/xml; charset=UTF-8' article.xml
+property 'svn:mime-type' set on 'article.xml'
+&prompt.user; svn propset fbsd:notbinary yes article.xml
+property 'fbsd:notbinary' set on 'article.xml'
+
+
+
+ Create a diff of these new files from the
+ ~/doc/ base directory:
+
+ &prompt.user; cd ~/doc
+svn diff ko_KR.UTF-8/articles/explaining-bsd > /tmp/ko-explaining.diff
+
+
+