Commit ea01277f authored by Sangdo Jun's avatar Sangdo Jun

translation hint

CVS version numbers

korean/devel/website/translation_hints.wml: INITIAL -> 1.1
parent 77ae8c7d
#use wml::debian::template title="쓸만한 번역 제안"
#include "$(ENGLISHDIR)/releases/info"
#use wml::debian::translation-check translation="1.38" maintainer="Sebul"
<p>번역에 제한되지 않는 관찰할 일반적인 것에 대한 <a href="working">웹 페이지에서 작업하기</a>에 관한 페이지를 보세요.
<h2>무엇을 번역할까?</h2>
<p>소개를 위해 <a href="translating#completenew">새 번역 시작 지침</a>을 참조하세요.</p>
<p>페이지를 번역하기 시작하면, 가장 많이 방문할 페이지부터 시작할 것을 권합니다.
여기에 몇 가이드라인이 있습니다;
<a href="stats/">번역 통계</a>의 페이지 목록은 인기순으로 정렬됩니다.</p>
<dt><strong>가장 중요:</strong></dt>
<li>주 디렉토리: index.wml, contact.wml, donations.wml,
social_contract.wml, support.wml</li>
<li>intro/ 디렉토리: about.wml, cn.wml, free.wml, why_debian.wml</li>
<li>releases/ 디렉토리: index.wml</li>
<li>releases/<current_release_name>/ 디렉토리: index.wml,
installmanual.wml, releasenotes.wml</li>
<li>distrib/ 디렉토리: index.wml, packages.wml, netinst.wml, ftplist.wml</li>
<li>mirror/ 디렉토리: list.wml</li>
<li>CD/ 디렉토리: index.wml</li>
<li>doc/ 디렉토리: index.wml</li>
<li>MailingLists/ 디렉토리: index.wml</li>
<li>security/ 디렉토리: index.wml</li>
<dd>앞에서 얘기한 디렉토리의 나머지 파일들, 그리고:
<li>Bugs/index.wml, Bugs/Reporting.wml</li>
<li>international/index.wml, and create a page (or directory) for your
<li>misc/index.wml, misc/related_links.wml</li>
<dd>All the other files in the previously mentioned directories.
This includes the following directories which include subdirectories that
are modified frequently, so are harder to keep up to date:
<dt><strong>가장 덜 중요:</strong></dt>
<dd>Files in the devel/ and vote/ directories. Since they are mostly
for developers, and the primary language of developers is English, it
is only when you have a strong translation team should you attempt to
tackle these.</dd>
<strong>It is important that you only translate files that you have
the time to maintain. A few well maintained pages is much more useful
than a lot of out of date ones.</strong>
<h2>How closely should translations follow the original?</h2>
<p>There are times when you may want to make a change to the content when
you are translating. One example is on the support page; you will probably
want to include an example on subscribing to the language specific mailing
list, e.g. debian-user-french on the French version of the pages.
<p>If you make more significant changes, please notify
<a href="">debian-www list</a>
as it is desired to keep the content as similar as possible
between the different versions.
<p>The pages are meant to be useful. If you have information that
will help the users of your language, feel free to add it. You can use
international/&lt;Language&gt;.wml for all the stuff interesting to
Language-speaking visitors.
<p>If you know of information that would be useful to all users,
bring it up on debian-www.
<h2>How do translators know when files need to be updated?</h2>
<P>There is a mechanism that translators can use to <a href="uptodate">
keeping web site translations up-to-date</a>.
<h2>How do we keep the gettext template translations up to date?</h2>
<p>After the English files have been updated, run <kbd>make update-po</kbd>
in the <code>po/</code> subdirectory of your translation to update your .po
files with the originals. Watching the log messages on the
<a href="">debian-www-cvs mailing
list</a> can be helpful to find out when this should be done; or you can
simply run it at regular intervals.</p>
<p>Use the <kbd>make stats</kbd> command to see an overview of the changes.
Gettext will mark the tags whose value it had to guess with
"<code>#, fuzzy</code>", and newly introduced tags will simply have an empty
string after <code>msgstr</code>.</p>
<h2>How do users know if a translated page is out of date?</h2>
<P>The <code>translation-check</code> template which is used to
<a href="uptodate">keep translations up-to-date</a> will make a note in
translations which are outdated.
<h2>번역 때 주의할 것</h2>
<p>The following is a list of pages and directories that may require special
attention when translating:
<dd>You can translate as many or as few pieces of news as you wish. The
indices are created automatically from the titles of the items. If an
item has been translated, then the translated title will be used in the
<dd>This is set up similar to the News/ directory. There's one
difference, there are .data files that you should <em>not</em> translate.</dd>
<dd>Only the *.wml files in CD/vendors/ should be translated.
Translations for tags are added via gettext in the
po/vendors.<var>xy</var>.po file.</dd>
<dd>Tags are translated via gettext in the
po/organization.<var>xy</var>.po file.</dd>
<dd>These two files are generated by the <tt>mklist</tt> script, so you
can't edit them directly. You can translate the files in the desc/
subdirectory, they contain the descriptions of mailing lists.
Tags are translated via gettext in the po/mailinglists.<var>xy</var>.po
<dd>Includes <tt>../../english/devel/people.names</tt> which is generated
daily by
<a href="">a
script parsing Packages files and the developers' database</a>.
Simply touch the people.names file if you want to build
<dd>Tags are translated via gettext in the po/consultants.<var>xy</var>.po
<dd>Translate everything but the Perl code (stuff enclosed in &lt;: :&gt;),
except for the <strong>second</strong> argument of permute_as_list.</dd>
<dd>Port pages may be volatile. You should only translate these if
you are willing to spend the time keeping them up to date.</dd>
<dd>This is for people editing or translating web pages, so it is
probably very low priority.</dd>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment