Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1512873 > unrolled thread

[PATCH v2 00/12] Fix and update HOWTO Korean translation

Back to article view | Back to linux.kernel

Contents

  [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park <sj38.park@gmail.com> - 2016-10-31 21:40 +0100
    [PATCH v2 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park <sj38.park@gmail.com> - 2016-10-31 21:40 +0100
    Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park <sj38.park@gmail.com> - 2016-11-06 19:30 +0100
      Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation Jonathan Corbet <corbet@lwn.net> - 2016-11-06 21:50 +0100
    Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation Jonathan Corbet <corbet@lwn.net> - 2016-11-08 01:10 +0100
      Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park <sj38.park@gmail.com> - 2016-11-08 03:30 +0100

#1512873 — [PATCH v2 00/12] Fix and update HOWTO Korean translation

This patchset applies ReST conversion effort for HOWTO document to its Korean
translation.  It also contains fixup of trivial nitpicks in the document and
the translation.

Changes from v1:
- Rebased on next-20161028
  The base version contains commit 186128f75392 ("docs-rst: add documents to
  development-process")

SeongJae Park (12):
  Documentation/process/howto: Mark subsection in suggested format
  ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds
  ko_KR/HOWTO: Fix subtitles style
  ko_KR/HOWTO: Update obsolete link to bugzilla faq
  ko_KR/HOWTO: Convert to ReST notation
  ko_KR/HOWTO: Add cross-references to other documents
  ko_KR/HOWTO: Update information about generating documentation
  ko_KR/HOWTO: Improve some markups to make it visually better
  ko_KR/HOWTO: Adjust external link references
  ko_KR/HOWTO: Clean up bare :: lines
  ko_KR/HOWTO: Add whitespace between URL and text
  ko_KR/HOWTO: Mark subsection in suggested format

 Documentation/ko_KR/HOWTO       | 162 ++++++++++++++++++++++++++--------------
 Documentation/process/howto.rst |  15 ++--
 2 files changed, 117 insertions(+), 60 deletions(-)

-- 
2.10.0

[toc] | [next] | [standalone]

#1512876 — [PATCH v2 07/12] ko_KR/HOWTO: Update information about generating documentation

This commit applies commit 43fb67a5258c ("Documentation/HOWTO: update
information about generating documentation") to Korean translation.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 Documentation/ko_KR/HOWTO | 30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
index 7f0b4e66e6c2..918be41b75de 100644
--- a/Documentation/ko_KR/HOWTO
+++ b/Documentation/ko_KR/HOWTO
@@ -176,21 +176,35 @@ mtk.manpages@gmail.com의 메인테이너에게 보낼 것을 권장한다.
     패치가 무엇이며 그것을 커널의 다른 개발 브랜치들에 어떻게
     적용하는지에 관하여 자세히 설명하고 있는 좋은 입문서이다.
 
-커널은 소스 코드 그 자체에서 자동적으로 만들어질 수 있는 많은 문서들을
-가지고 있다. 이것은 커널 내의 API에 대한 모든 설명, 그리고 락킹을
-올바르게 처리하는 법에 관한 규칙을 포함하고 있다. 이 문서는
-Documentation/DocBook/ 디렉토리 내에서 만들어지며 PDF, Postscript, HTML,
-그리고 man 페이지들로 다음과 같이 실행하여 만들어 진다.
+커널은 소스 코드 그 자체에서 또는 이것과 같은 ReStructuredText 마크업 (ReST) 을
+통해 자동적으로 만들어질 수 있는 많은 문서들을 가지고 있다. 이것은 커널 내의
+API에 대한 모든 설명, 그리고 락킹을 올바르게 처리하는 법에 관한 규칙을 포함하고
+있다.
+
+모든 그런 문서들은 커널 소스 디렉토리에서 다음 커맨드를 실행하는 것을 통해 PDF
+나 HTML 의 형태로 만들어질 수 있다.
 
 ::
 
          make pdfdocs
-         make psdocs
          make htmldocs
-         make mandocs
 
-각각의 명령을 메인 커널 소스 디렉토리로부터 실행한다.
+ReST 마크업을 사용하는 문서들은 Documentation/output 에 생성된다.  해당
+문서들은 다음의 커맨드를 사용하면 LaTeX 이나 ePub 로도 만들어질 수 있다:
+
+::
+
+         make latexdocs
+         make epubdocs
+
+현재, ReST 로의 변환이 진행중인, DocBook 으로 쓰인 문서들이 존재한다. 그런
+문서들은 Documentation/DocBook/ 디렉토리 안에 생성될 것이고 다음 커맨드를 통해
+Postscript 나 man page 로도 만들어질 수 있다:
+
+::
 
+         make psdocs
+         make mandocs
 
 커널 개발자가 되는 것
 ---------------------
-- 
2.10.0

[toc] | [prev] | [next] | [standalone]

#1515731

May I ask some comments, please?


Thanks,
SeongJae Park

On Tue, Nov 1, 2016 at 5:27 AM, SeongJae Park <sj38.park@gmail.com> wrote:
> This patchset applies ReST conversion effort for HOWTO document to its Korean
> translation.  It also contains fixup of trivial nitpicks in the document and
> the translation.
>
> Changes from v1:
> - Rebased on next-20161028
>   The base version contains commit 186128f75392 ("docs-rst: add documents to
>   development-process")
>
> SeongJae Park (12):
>   Documentation/process/howto: Mark subsection in suggested format
>   ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds
>   ko_KR/HOWTO: Fix subtitles style
>   ko_KR/HOWTO: Update obsolete link to bugzilla faq
>   ko_KR/HOWTO: Convert to ReST notation
>   ko_KR/HOWTO: Add cross-references to other documents
>   ko_KR/HOWTO: Update information about generating documentation
>   ko_KR/HOWTO: Improve some markups to make it visually better
>   ko_KR/HOWTO: Adjust external link references
>   ko_KR/HOWTO: Clean up bare :: lines
>   ko_KR/HOWTO: Add whitespace between URL and text
>   ko_KR/HOWTO: Mark subsection in suggested format
>
>  Documentation/ko_KR/HOWTO       | 162 ++++++++++++++++++++++++++--------------
>  Documentation/process/howto.rst |  15 ++--
>  2 files changed, 117 insertions(+), 60 deletions(-)
>
> --
> 2.10.0
>

[toc] | [prev] | [next] | [standalone]

#1515762

On Mon, 7 Nov 2016 03:21:32 +0900
SeongJae Park <sj38.park@gmail.com> wrote:

> May I ask some comments, please?

Sorry, last week was the kernel summit and plumbers, so I'm behind on a
lot of things.  I'll get there.

jon

[toc] | [prev] | [next] | [standalone]

#1516693

On Tue,  1 Nov 2016 05:27:09 +0900
SeongJae Park <sj38.park@gmail.com> wrote:

> This patchset applies ReST conversion effort for HOWTO document to its Korean
> translation.  It also contains fixup of trivial nitpicks in the document and
> the translation.

OK, to the extent that I can understand them, these changes all seem
reasonable to me, and I'll be happy to apply them.  Indeed, I have just
done so.

They stop short of the final step, though: actually hooking the
ReST-formatted file into the build system.  I would envision something
like this:

 - Create a new directory Documentation/translations (or something like
   "trans" if we want to be shorter, but I think it makes sense to spell
   it out).

 - Move ja_JP, ko_KR, and zh_CN into that directory

 - Rename .../ko_KR/HOWTO to HOWTO.rst

 - Create an overall index.rst for Korean translations.  It could include
   information on how the translations are done, who to contact, and pull
   in the translated HOWTO document.

 - Add that index.rst to the top-level build.  (We could consider putting
   an index file in translations/ as well, but that can come later).

Make sense?  I may do this in the not-too-near future if nobody else beats
me to it, but I'd welcome patches.

Thanks, 

jon

[toc] | [prev] | [next] | [standalone]

#1516743

On Tue, Nov 8, 2016 at 9:05 AM, Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue,  1 Nov 2016 05:27:09 +0900
> SeongJae Park <sj38.park@gmail.com> wrote:
>
>> This patchset applies ReST conversion effort for HOWTO document to its Korean
>> translation.  It also contains fixup of trivial nitpicks in the document and
>> the translation.
>
> OK, to the extent that I can understand them, these changes all seem
> reasonable to me, and I'll be happy to apply them.  Indeed, I have just
> done so.

Thanks.


>
> They stop short of the final step, though: actually hooking the
> ReST-formatted file into the build system.  I would envision something
> like this:
>
>  - Create a new directory Documentation/translations (or something like
>    "trans" if we want to be shorter, but I think it makes sense to spell
>    it out).
>
>  - Move ja_JP, ko_KR, and zh_CN into that directory
>
>  - Rename .../ko_KR/HOWTO to HOWTO.rst
>
>  - Create an overall index.rst for Korean translations.  It could include
>    information on how the translations are done, who to contact, and pull
>    in the translated HOWTO document.
>
>  - Add that index.rst to the top-level build.  (We could consider putting
>    an index file in translations/ as well, but that can come later).
>
> Make sense?  I may do this in the not-too-near future if nobody else beats
> me to it, but I'd welcome patches.

Yes, it makes sense as I agreed before.  I am preparing patches for that and
will send the patches by tomorrow.


Thanks,
SeongJae Park

>
> Thanks,
>
> jon

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web