[perl.git] branch blead, updated. v5.19.1-258-g531e207

Thu, 04 Jul 2013 18:33:50 -0700 

In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/531e2078f59379db6eff2b836b2a0e74ef3d3c52?hp=247f9b19318882fd9a52fe49aa31fc8d3d3db4f7>

- Log -----------------------------------------------------------------
commit 531e2078f59379db6eff2b836b2a0e74ef3d3c52
Author: Father Chrysostomos <[email protected]>
Date:   Thu Jul 4 18:30:56 2013 -0700

    Consistent spaces after dots in perlhack.pod

M       pod/perlhack.pod

commit cfb69a0266f23f294bcf0d6d8c5216c31b81e84c
Author: Father Chrysostomos <[email protected]>
Date:   Thu Jul 4 18:25:30 2013 -0700

    Use tabs consistently in AUTHORS

M       AUTHORS

commit c25624d12c5d5fce720283f042178445c73689c0
Author: Father Chrysostomos <[email protected]>
Date:   Thu Jul 4 18:25:16 2013 -0700

    README.ko: remove blank line
    
    This fixes a completely bogus failure from podcheck.t, something about
    a verbatim section under NAME.

M       README.ko

commit e9da8ca7b8178de66eb55e3ff739ce049f76b7e3
Author: Father Chrysostomos <[email protected]>
Date:   Thu Jul 4 13:22:39 2013 -0700

    Add Keedi Kim to AUTHORS

M       AUTHORS

commit 277d344a7138edb0db4be779195187fb483a21cd
Author: Keedi Kim <[email protected]>
Date:   Fri Jul 5 02:11:12 2013 +0900

    Update brand-new README.ko

M       README.ko
-----------------------------------------------------------------------

Summary of changes:
 AUTHORS          |   3 +-
 README.ko        | 338 +++++++++++++++++++++++++++++++++++++++----------------
 pod/perlhack.pod | 212 +++++++++++++++++-----------------
 3 files changed, 346 insertions(+), 207 deletions(-)

diff --git a/AUTHORS b/AUTHORS
index 13f0c15..01b6e1d 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -163,7 +163,7 @@ Brian Carlson                       
<[email protected]>
 Brian Clarke                   <[email protected]>
 brian d foy                    <[email protected]>
 Brian Fraser                   <[email protected]>
-Brian Gottreu                   <[email protected]>
+Brian Gottreu                  <[email protected]>
 Brian Greenfield               <[email protected]>
 Brian Grossman
 Brian Harrison                 <[email protected]>
@@ -638,6 +638,7 @@ Karthik Rajagopalan         
<[email protected]>
 Kaveh Ghazi                    <[email protected]>
 Kay Röpke                     <[email protected]>
 KAWAI Takanori                 <[email protected]>
+Keedi Kim                      <[email protected]>
 Keith Neufeld                  <[email protected]>
 Keith Thompson                 <[email protected]>
 Ken Estes                      <[email protected]>
diff --git a/README.ko b/README.ko
index 2632135..daedf0f 100644
--- a/README.ko
+++ b/README.ko
@@ -1,201 +1,339 @@
 =encoding utf8
 
-이 문서를 perldoc을 써서 보지 않고 직접 보는 경우에는 각 
부분의
-역할을 표시하기 위해 쓰인 =head, =item, 'L' 등은 
무시하십시오.
-이 문서는 따로 perldoc을 쓰지 않고 보더라도 읽는데 별 
지장이
-없는 POD 형식으로 짜여 있습니다.  더 자세한 것은 perlpod
-매뉴얼을 참고하십시오. 
+이 파일을 내용 그대로 읽고 있다면 우스꽝스러운 문자는 
무시해주세요.
+이 문서는 POD로 읽을 수 있도록 POD 형식(F<pod/perlpod.pod> 
문서를
+확인하세요)으로 작성되어 있습니다.
+
 
 =head1 NAME
 
-perlko - Perl과 한국어 인코딩
+perlko - 한국어 Perl 안내서
 
 =head1 DESCRIPTION
 
-Perl의 세계에 오신 것을 환영합니다 !
+Perl의 세계에 오신 것을 환영합니다!
+
+Perl은 가끔 B<'Practical Extraction and Report Language'>라고 하기도 
합니다만
+다른 널리 알려진 것들 중에서 B<'Pathologically Eclectic Rubbish 
Lister'>라고
+하기도 합니다. 사실 이것은 끼워 맞춘 것이며 Perl이 
이것들의 첫 글자를
+가져와서 이름을 붙인 것은 아닙니다. Perl의 창시자 Larry가 
첫 번째 이름을
+먼저 생각했고 널리 알려진 것을 나중에 지었기 때문입
니다. 그렇기 때문에
+B<'Perl'>은 모두 대문자가 아닙니다. 널리 알려진 어떤 것을 
가지고 논쟁하는
+것은 의미가 없습니다. Larry는 두 개 다 지지합니다.
+
+가끔 p가 소문자로 작성된 B<'perl'>을 볼 것입니다. P가 
대문자로 되어 있는
+B<'Perl'>은 언어를 참조할 때 쓰이며 B<'perl'>처럼 p가 
소문자인 경우는 여러분의
+프로그램을 컴파일하고 돌릴 때 사용되는 해석기를 지칭할 
때 사용됩니다.
+
+
+=head1 Perl에 관하여
+
+Perl은 본래 문자열 생성을 위해 만들졌지만 지금은 시스템 
관리와 웹 개발,
+네트워크 프로그래밍, GUI 개발 등을 포함한 여러 분야에서 
널리 사용되는
+범용 프로그래밍 언어입니다.
+
+이 언어는 아름다움(아주 작고, 우아하고, 아주 적고)보다
+실용적(사용하기 쉽고, 효율적이며, 가능한 최대한)인 것을 
지향하고 있습니다.
+사용하기 쉽고, 절차적 프로그래밍과 객체 지향 
프로그래밍을 모두 지원하고,
+강력한 문자열 처리 기능을 내장하고, 세상에서 가장 인상ì 
ì¸ 제 3자의 모듈
+모음처를 가지고 있다는 것은 Perl의 가장 중요한 특징입
니다.
+
+Perl의 언어적 특징은 F<pod/perlintro.pod> 문서에서 소개합니다.
+
+이번 릴리스에서 가장 중요한 변화는 F<pod/perldelta.pod>에서 ë…
¼ì˜í•©ë‹ˆë‹¤.
+
+또한 다양한 출판사가 출판한 많은 Perl 책은 다양한 주제를 
다루고 있습니다.
+자세한 정보는 F<pod/perlbook.pod> 문서를 확인하세요.
+
+
+=head1 설치
+
+여러분이 비교적 현대의 운영체제를 사용하고 있고 현재 
버전의 Perl을
+지역적으로 설치하고 싶다면 다음 명령을 실행하세요.
+
+    ./Configure -des -Dprefix=$HOME/localperl
+    make test
+    make install
+
+앞의 명령은 여러분의 플랫폼에 맞게 환경을 설정하고 
컴파일을 수행한 후,
+회기 테스트를 수행한뒤, 홈 디렉터리 하부의 F<localperl> 디ë 
‰í„°ë¦¬ì— perl을
+설치합니다.
+
+여러분이 어떠한 문제든 겪게 되거나 사용자 정의 버전 
Perl을 설치할 필요가 있다면
+현재 배포판에 들어있는 F<INSTALL> 파일 안의 자세한 설명을 
읽어야 합니다.
+추가적으로 일반적이지 않은 다양한 플랫폼에서 Perl을 
빌드하고 사용하는
+방법에 대한 도움말과 귀띔이 적혀있는 많은 수의 F<README> 
파일이 있습니다.
+
+일단 Perl을 설치하고 나면 C<perldoc> 도구를 이용해 풍부한 
문서를 사용할
+수 있습니다. 시작하기 위해서 다음 명령을 실행하세요.
 
+    perldoc perl
 
-Perl은 5.8.0판부터 유니코드/ISO 10646에 대한 광범위한 지원을 
합니다.
+
+=head1 실행에 어려움을 겪는다면
+
+Perl은 뜨개질에서 부터 로켓 과학까지 모든 분야에서 
사용할 수 있는 크고
+복잡한 시스템입니다. 여러분이 어려움에 부딪혔을때 그 
문제는 이미 다른
+사람이 해결했을 가능성이 높습니다. 문서를 모두 
확인했는데도 버그가
+확실하다면 C<perlbug> 도구를 이용해서 저희에게 버그를 보고
해주세요.
+C<perlbug>에 대한 더 자세한 정보는 C<perldoc perlbug> 또는 
C<perlbug>를
+명령줄에서 실행해서 확인할 수 있습니다.
+
+Perl을 사용 가능하게 만들었다 하더라도 Perl은 계속해서 
진화하기 때문에
+여러분이 맞닥뜨린 버그를 수정했거나 여러분이 유
용하다고 생각할법한
+새로운 기능이 추가된 좀 더 최신 버전이 있을 수 있습니다.
+
+여러분은 항상 최신 버전의 perl을 CPAN (Comprehensive Perl Archive 
Network)
+사이트 L<http://www.cpan.org/src/> 에서 찾을 수 있습니다.
+
+perl 소스에 간단한 패치를 등록하고 싶다면 F<pod/perlhack.pod> 
문서의
+B<"SUPER QUICK PATCH GUIDE">를 살펴보세요.
+
+그냥 개인적으로 참고하세요.
+제가 이것처럼 멋진 물건을 만든다는 것을 여러분이 
알기를 바랍니다.
+그것은 제 이야기의 B<"저자(Author)">를 기쁘게하기 때문입
니다.
+이것이 여러분을 귀찮게 한다면 여러분의 B<"ì 
€ìž‘(Authorship)">에
+대한 생각을 정정해야 할 수도 있습니다. 하지만 어쨌거나 
여러분은
+Perl을 사용하는데는 문제가 없답니다. :-)
+
+- B<"저자">로부터.
+
+
+=head1 인코딩
+
+Perl은 5.8.0판부터 유니코드/ISO 10646에 대해 광범위하게 
지원합니다.
 유니코드 지원의 일환으로 한중일을 비롯한 세계 각국에서
 유니코드 이전에 쓰고 있었고 지금도 널리 쓰이고 있는 
수많은 인코딩을
-지원합니다.  유니코드는 전 세계에서 쓰이는 모든 언어를 
위한 표기 체계 -
-유럽의 라틴 알파벳, 키릴 알파벳, 그리스 알파벳, 인도와 
동남 아시아의
+지원합니다. 유니코드는 전 세계에서 쓰이는 모든 언어를 
위한
+표기 체계(유럽의 라틴 알파벳, 키릴 알파벳, 그리스 
알파벳, 인도와 동남 아시아의
 브라미 계열 스크립트, 아랍 문자, 히브리 문자, 한중일의 
한자, 한국어의 한글,
-일본어의 가나, 북미 인디안의 표기 체계 등-를 수용하는 
것을 목표로 하고
+일본어의 가나, 북미 인디안의 표기 체계 등)를 수용하는 
것을 목표로 하고
 있기 때문에 기존에 쓰이던  각 언어 및 국가 그리고 운영 
체계에 고유한
 문자 집합과 인코딩에 쓸 수 있는 모든 글자는 물론이고  
기존 문자 집합에서
 지원하고 있지 않던 아주 많은 글자를  포함하고 있습니다.
 
-
-Perl은 내부적으로 유니코드를 문자 표현을 위해 
사용합니다. 보다 구체적으로
-말하면 Perl 스크립트 안에서  UTF-8 문자열을 쓸 수 있고, 
+Perl은 내부적으로 유니코드를 문자 표현을 위해 
사용합니다.
+보다 구체적으로 말하면 Perl 스크립트 안에서  UTF-8 
문자열을 쓸 수 있고,
 각종 함수와 연산자(예를 들어, 정규식, index, substr)가 
바이트 단위
-대신 유니코드 글자 단위로 동작합니다. (더 자세한 것은 
-perlunicode 매뉴얼을 참고하십시오.) 유니코드가 널리 
보급되기 전에
-널리 쓰이고 있었고, 여전히 널리 쓰이고 있는 각국/각 
언어별 인코딩으로
-입출력을 하고 이들 인코딩으로 된 데이터와 문서를 
다루는 것을 돕기 위해
-'Encode'가  쓰였습니다. 무엇보다 'Encode'를  써서 수많은 
인코딩 사이의
-변환을 쉽게 할 수 있습니다.
+대신 유니코드 글자 단위로 동작합니다.
+더 자세한 것은 F<pod/perlunicode.pod> 문서를 참고하세요.
+유니코드가 널리 보급되기 전에 널리 쓰이고 있었고, 여ì 
„히 널리 쓰이고 있는
+각국/각 언어별 인코딩으로 입출력을 하고 이들 
인코딩으로 된 데이터와 문서를
+다루는 것을 돕기 위해 L<Encode> 모듈이 쓰이고 있습니다.
+무엇보다 L<Encode> 모듈을 사용하면 수많은 인코딩 사이의 
변환을 쉽게 할 수 있습니다.
+
+
+=head2 Encode 모듈
 
-'Encode'는 다음과 같은 한국어 인코딩을 지원합니다.
+=head3 지원 인코딩
+
+L<Encode> 모듈은 다음과 같은 한국어 인코딩을 지원합니다.
 
 =over 4
 
-=item * euc-kr 
+=item * C<euc-kr>
 
-US-ASCII와 KS X 1001을 같이 쓰는 멀티바이트 인코딩 (흔히 
완성형이라고
-불림.) KS X 2901과 RFC 1557 참고.
+US-ASCII와 KS X 1001을 같이 쓰는 멀티바이트 인코딩으로 흔히
+완성형이라고 불림. KS X 2901과 RFC 1557 참고.
 
-=item * cp949     
+=item * C<cp949>
 
-MS-Windows 9x/ME에서 쓰이는 확장 완성형.  euc-kr에 8,822자의
-한글 음절을 더한 것임.  alias는 uhc, windows-949, x-windows-949,
+MS-Windows 9x/ME에서 쓰이는 확장 완성형. euc-kr에 8,822자의
+한글 음절을 더한 것임. alias는 uhc, windows-949, x-windows-949,
 ks_c_5601-1987. 맨 마지막 이름은 적절하지 않은 이름이지만, 
Microsoft
 제품에서 CP949의 의미로 쓰이고 있음.
 
-=item * johab          
+=item * C<johab>
 
-KS X 1001:1998 부록 3에서 규정한 조합형.  문자 레퍼토리는 
cp949와
-마찬가지로 US-ASCII와  KS X 1001에 8,822자의 한글 음절을 더한 
것임.
-인코딩 방식은 전혀 다름. 
+KS X 1001:1998 부록 3에서 규정한 조합형. 문자 레퍼토리는 
cp949와 마찬가지로
+US-ASCII와  KS X 1001에 8,822자의 한글 음절을 더한 것으로 
인코딩 방식은 전혀 다름.
 
-=item * iso-2022-kr     
+=item * C<iso-2022-kr>
 
 RFC 1557에서 규정한 한국어 인터넷 메일 교환용 인코딩으로 
US-ASCII와
 KS X 1001을 레퍼토리로 하는 점에서 euc-kr과 같지만 인코딩 
방식이 다름.
 1997-8년 경까지 쓰였으나 더 이상 메일 교환에 쓰이지 않음.
 
-=item * ksc5601-raw     
+=item * C<ksc5601-raw>
 
-KS X 1001(KS C 5601)을 GL(즉, MSB를 0으로 한 경우) 에 놓았을 때의
-인코딩. US-ASCII와 결합하지 않고 단독으로 쓰이는 일은 X11 
등에서 글꼴
-인코딩 (ksc5601.1987-0. '0'은 GL을 의미함.)으로 쓰이는 것을 ì 
œì™¸í•˜ê³ ëŠ”
-거의 없음. KS C 5601은 1997년 KS X 1001로 이름을 바꾸었음.  
1998년에는  두
-글자 (유로화 부호와 등록 상표 부호)가 더해졌음.
+KS X 1001(KS C 5601)을 GL(즉, MSB를 0으로 한 경우)에 놓았을 때의 
인코딩.
+US-ASCII와 결합하지 않고 단독으로 쓰이는 일은 X11 등에서 
글꼴
+인코딩(ksc5601.1987-0. '0'은 GL을 의미함)으로 쓰이는 것을 ì 
œì™¸í•˜ê³ ëŠ”
+거의 없음. KS C 5601은 1997년 KS X 1001로 이름을 바꾸었음. 1998ë…
„에는 두
+글자(유로화 부호와 등록 상표 부호)가 더해졌음.
 
 =back
 
-몇 가지 사용 예제를 아래에 보입니다. 
+=head3 변환 예제
 
-예를 들어, euc-kr 인코딩으로 된 파일을 UTF-8로 변환하려면 
다음과
-같이 하면 됩니다. 
+예를 들어, euc-kr 인코딩으로 된 파일을 UTF-8로 변환하려면
+명령줄에서 다음처럼 실행합니다.
 
+    perl -Mencoding=euc-kr,STDOUT,utf8 -pe1 < file.euc-kr > file.utf8
 
-    perl -Mencoding=euc-kr,STDOUT,utf8 -pe1  < file.euckr > file.utf8
+반대로 변환할 경우 다음처럼 실행합니다.
 
-역변환은 다음과 같이 할 수 있습니다. 
+    perl -Mencoding=utf8,STDOUT,euc-kr -pe1 < file.utf8 > file.euc-kr
 
-    perl -Mencoding=utf8,STDOUT,euc-kr -pe1  < file.utf8  > file.euckr
+이런 변환을 좀더 편리하게 할 수 있도록 도와주는 
F<piconv>가 Perl에
+기본으로 들어있습니다. 이 유틸리티는 L<Encode> 모듈을 
이용한 순수 Perl
+유틸리티로 이름에서 알 수 있듯이 Unix의 C<iconv>를 모델로 
한 것입니다.
+사용법은 다음과 같습니다.
 
-이런 변환을 좀더 편리하게 할 수 있도록 Encode 모듈을 써서 
-순수하게 Perl로만 쓰인 piconv가 Perl에 들어 있습니다.
-그 이름에서 알 수 있듯이 piconv는 Unix에 있는 iconv를
-모델로 한 것입니다. 그 사용법은 아래와 같습니다.
+   piconv -f euc-kr -t utf8 < file.euc-kr > file.utf8
+   piconv -f utf8 -t euc-kr < file.utf8 > file.euc-kr
 
-   piconv -f euc-kr -t utf8 < file.euckr > file.utf8
-   piconv -f utf8 -t euc-kr < file.utf8 > file.euckr
+=head3 모범 사례
 
-또, 'PerlIO::encoding' 모듈을 써서 한국어 인코딩을 쓰면서 
글자 단위
-(바이트 단위가 아니라) 처리를 쉽게 할 수 있습니다.
+Perl은 기본적으로 내부에서 UTF-8을 사용하며 Encode 모듈을 
통해
+다양한 인코딩을 지원하지만 항상 다음 규칙을 지킴으로써 
인코딩과
+관련한 다양하게 발생할 수 있는 문제의 가능성을 줄이는 
것을 추천합니다.
 
-  #!/path/to/perl 
+=over 4
 
-  use encoding 'euc-kr', STDIN => 'euc-kr',
-                         STDOUT-> 'euc-kr', STDERR=>'euc-kr';
+=item * 소스 코드는 항상 UTF-8 인코딩으로 저장
 
-  print length("가나");        # 2  (큰 따옴표는 글자 단위 
처리를 지시)
-  print length('가나');        # 4  (작은 따옴표는 바이트 단위 
처리를 지시)
-  print index("한강, 대동강", "염");   # -1 ('염'이 없음)
-  print index('한강, 대동강', '염');   # 7 (8번째와 9번째 
바이트가 '염'의
-                                            코드값과 일치함.)
+=item * 소스 코드 상단에 C<use utf8;> 프라그마 사용
 
+=item * 소스 코드, 터미널, 운영체제, 데이터 인코딩을 
분리해서 이해
 
-=head2 더 자세히 알고 싶으면...
+=item * 입출력 파일 핸들에 명시적인 인코딩을 사용
 
-Perl을 설치하면  대단히 자세한 문서가 같이 따라 오며, 이 
문서를 통해
-Perl 전반 뿐 아니라 유니코드 지원, Encode의 사용법 등에 
많은 것을
-배울 수 있습니다.  아직 이 문서는 현재 모두 영어로 쓰여 
있습니다.
+=item * 중복(double) 인코딩을 주의
 
+=back
 
-=head2 Perl 관련 자료
 
-위에서 언급한  문서 외에도 다음과 같은 자료가 있습니다. 
이 목록은 결코
-완전한 것이 아니고 일부 대표적인 것만 모은 것입니다.
+=head3 유니코드 및 한국어 인코딩 관련 자료
 
 =over 4
 
-=item L<http://www.perl.com/>          
+=item * L<perluniintro>
+
+=item * L<perlunicode>
 
-   O'Reilly의 Perl 웹 페이지 
+=item * L<Encode>
 
-=item L<http://www.cpan.org/>
+=item * L<Encode::KR>
 
-       Comprehensive Perl Archive Network
+=item * L<encoding>
 
-=item L<http://lists.perl.org/>        
+=item * L<http://www.unicode.org/>
 
-  Perl 메일링 리스트. 많은 리스트 가운데
-  perl-unicode에서 'Encode'에 대해 논의함.
+유니코드 컨소시엄
+
+=item * L<http://std.dkuug.dk/JTC1/SC2/WG2>
+
+기본적으로 Unicode와 같은 ISO 표준인  ISO/IEC 10646 UCS(Universal
+Character Set)을 만드는 ISO/IEC JTC1/SC2/WG2의 웹 페이지
+
+=item * L<http://www.cl.cam.ac.uk/~mgk25/unicode.html>
+
+유닉스/리눅스 사용자를 위한 UTF-8 및 유니코드 관련 FAQ
+
+=item * 
L<http://wiki.kldp.org/Translations/html/UTF8-Unicode-KLDP/UTF8-Unicode-KLDP.html>
+
+유닉스/리눅스 사용자를 위한 UTF-8 및 유니코드 관련 FAQ의 
한국어 번역
 
 =back
 
-=head2 Perl을 더 깊게 공부하는데 도움을 줄 수 있는 한국어 
관련 사이트
+
+=head1 Perl 관련 자료
+
+다음은 공식적인 Perl 관련 자료중 일부입니다.
 
 =over 4
 
-=item L<http://www.perl.or.kr/>
+=item * L<http://www.perl.org/>
 
-  Perl 한국 사용자 모임 
+Perl 공식 홈페이지
 
-=item L<news:han.comp.lang.perl/>
+=item * L<http://www.perl.com/>
 
-  한국어 Perl 뉴스 그룹
+O'Reilly의 Perl 웹 페이지
 
-=item L<http://www.hanb.co.kr/search/searchResult.html?keyword=perl>
+=item * L<http://www.cpan.org/>
 
-  O'Reilly에서 나온 한국어 Perl 서적 목록
+CPAN - Comprehensive Perl Archive Network, 통합적 Perl 파일 보관 
네트워크
 
-=item L<http://www.perlschool.net/>
+=item * L<http://metacpan.org>
 
-  Perl 기초 강좌 및 소스, 최근 동향, 관련 해외 사이트 링크 
+메타 CPAN
 
-=item L<http://www.perl.co.kr>
+=item * L<http://lists.perl.org/>
 
-  Perl에 관련된 CGI, DB, 연동 등에 대한  정보 및 뉴스 제공
+Perl 메일링 리스트
 
-=back 
+=item * L<http://blogs.perl.org/>
 
-=head2 유니코드 및 한국어 인코딩 관련 자료
+Perl 메타 블로그
+
+=item * L<http://www.perlmonks.org/>
+
+Perl 수도승들을 위한 수도원
+
+=item * L<http://www.pm.org/groups/asia.html>
+
+아시아 지역 Perl 몽거스 모임
+
+=item * L<http://www.perladvent.org/>
+
+Perl 크리스마스 달력
+
+=back
+
+
+다음은 Perl을 더 깊게 공부하는데 도움을 줄 수 있는 
한국어 관련 사이트입니다.
 
 =over 4
 
-=item L<http://www.unicode.org/>
+=item * L<http://perl.kr/>
 
-  유니코드 컨소시엄.  
+한국 Perl 커뮤니티 공식 포털
 
-=item L<http://std.dkuug.dk/JTC1/SC2/WG2>
+=item * L<http://doc.perl.kr/>
 
-기본적으로 Unicode와 같은 ISO 표준인  ISO/IEC 10646 UCS(Universal
-Character Set)을 만드는  ISO/IEC JTC1/SC2/WG2의 웹 페이지. 
+Perl 문서 한글화 프로젝트
+
+=item * L<http://cafe.naver.com/perlstudy.cafe>
+
+네이버 Perl 카페
+
+=item * L<http://www.perl.or.kr/>
+
+한국 Perl 사용자 모임
+
+=item * L<http://advent.perl.kr>
 
-=item L<http://www.cl.cam.ac.uk/~mgk25/unicode.html>
+Seoul.pm Perl 크리스마스 달력 (2010 ~ 2012)
 
-  유닉스/리눅스에서 유니코드와 UTF-8 사용에 대한 
문답집(FAQ)
+=item * L<http://gypark.pe.kr/wiki/Perl>
 
-=item 
L<http://wiki.kldp.org/Translations/html/UTF8-Unicode-KLDP/UTF8-Unicode-KLDP.html>
+GYPARK(Geunyoung Park)의 Perl 관련 한글 문서 저장소
 
-  유닉스/리눅스에서 유니코드와 UTF-8 사용에 대한 
문답집(FAQ)의  한국어 번역
+=item * L<http://seoul.pm.org>
+
+Seoul.pm - 서울 Perl 몽거스
 
 =back
 
-=head1 SEE ALSO
 
-L<Encode>, L<Encode::KR>, L<encoding>, L<perluniintro>, L<perlunicode>
+=head1 라이센스
+
+F<README> 파일의 B<'LICENSING'> 항목을 참고하세요.
 
 
 =head1 AUTHORS
 
-Jarkko Hietaniemi E<lt>[email protected]<gt>
-신정식 E<lt>[email protected]<gt>
+=over
+
+=item * Jarkko Hietaniemi E<lt>[email protected]<gt>
+
+=item * 신정식 E<lt>[email protected]<gt>
+
+=item * 김도형 E<lt>[email protected]<gt>
+
+=back
+
 
 =cut
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 22bb8b6..6403bb1 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -10,7 +10,7 @@ perlhack - How to hack on Perl
 
 =head1 DESCRIPTION
 
-This document explains how Perl development works. It includes details
+This document explains how Perl development works.  It includes details
 about the Perl 5 Porters email list, the Perl repository, the Perlbug
 bug tracker, patch guidelines, and commentary on Perl development
 philosophy.
@@ -24,7 +24,7 @@ for a bug, comment fixes, etc., it's easy! Here's how:
 
 =item * Check out the source repository
 
-The perl source is in a git repository. You can clone the repository
+The perl source is in a git repository.  You can clone the repository
 with the following command:
 
   % git clone git://perl5.git.perl.org/perl.git perl
@@ -49,7 +49,7 @@ Committing your work will save the change I<on your local 
system>:
   % git commit -a -m 'Commit message goes here'
 
 Make sure the commit message describes your change in a single
-sentence. For example, "Fixed spelling errors in perlhack.pod".
+sentence.  For example, "Fixed spelling errors in perlhack.pod".
 
 =item * Send your change to perlbug
 
@@ -64,7 +64,7 @@ subject:
  % perlbug -s "[PATCH] $(git log -1 --oneline HEAD)" -f 0001-*.patch
 
 The perlbug program will ask you a few questions about your email
-address and the patch you're submitting. Once you've answered them it
+address and the patch you're submitting.  Once you've answered them it
 will submit your patch via email.
 
 =item * Thank you
@@ -77,29 +77,29 @@ Thank you!
 =head1 BUG REPORTING
 
 If you want to report a bug in Perl, you must use the F<perlbug>
-command line tool. This tool will ensure that your bug report includes
+command line tool.  This tool will ensure that your bug report includes
 all the relevant system and configuration information.
 
 To browse existing Perl bugs and patches, you can use the web interface
 at L<http://rt.perl.org/>.
 
 Please check the archive of the perl5-porters list (see below) and/or
-the bug tracking system before submitting a bug report. Often, you'll
+the bug tracking system before submitting a bug report.  Often, you'll
 find that the bug has been reported already.
 
 You can log in to the bug tracking system and comment on existing bug
-reports. If you have additional information regarding an existing bug,
-please add it. This will help the porters fix the bug.
+reports.  If you have additional information regarding an existing bug,
+please add it.  This will help the porters fix the bug.
 
 =head1 PERL 5 PORTERS
 
 The perl5-porters (p5p) mailing list is where the Perl standard
-distribution is maintained and developed. The people who maintain Perl
+distribution is maintained and developed.  The people who maintain Perl
 are also referred to as the "Perl 5 Porters", "p5p" or just the
 "porters".
 
 A searchable archive of the list is available at
-L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/>. There is
+L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/>.  There is
 also another archive at
 L<http://archive.develooper.com/[email protected]/>.
 
@@ -107,7 +107,7 @@ L<http://archive.develooper.com/[email protected]/>.
 
 The perl5-changes mailing list receives a copy of each patch that gets
 submitted to the maintenance and development branches of the perl
-repository. See L<http://lists.perl.org/list/perl5-changes.html> for
+repository.  See L<http://lists.perl.org/list/perl5-changes.html> for
 subscription and archive information.
 
 =head2 #p5p on IRC
@@ -119,7 +119,7 @@ Perl core.
 =head1 GETTING THE PERL SOURCE
 
 All of Perl's source code is kept centrally in a Git repository at
-I<perl5.git.perl.org>. The repository contains many Perl revisions from
+I<perl5.git.perl.org>.  The repository contains many Perl revisions from
 Perl 1 onwards and all the revisions from Perforce, the previous
 version control system.
 
@@ -128,7 +128,7 @@ L<perlgit>.
 
 =head2 Read access via Git
 
-You will need a copy of Git for your computer. You can fetch a copy of
+You will need a copy of Git for your computer.  You can fetch a copy of
 the repository using the git protocol:
 
   % git clone git://perl5.git.perl.org/perl.git perl
@@ -143,10 +143,10 @@ clone via http, though this is much slower:
 
 =head2 Read access via the web
 
-You may access the repository over the web. This allows you to browse
+You may access the repository over the web.  This allows you to browse
 the tree, see recent commits, subscribe to RSS feeds for the changes,
-search for particular commits and more. You may access it at
-L<http://perl5.git.perl.org/perl.git>. A mirror of the repository is
+search for particular commits and more.  You may access it at
+L<http://perl5.git.perl.org/perl.git>.  A mirror of the repository is
 found at L<http://github.com/mirrors/perl>.
 
 =head2 Read access via rsync
@@ -175,38 +175,38 @@ using git.
 =head1 PATCHING PERL
 
 If you're planning to do more extensive work than a single small fix,
-we encourage you to read the documentation below. This will help you
+we encourage you to read the documentation below.  This will help you
 focus your work and make your patches easier to incorporate into the
 Perl source.
 
 =head2 Submitting patches
 
-If you have a small patch to submit, please submit it via perlbug. You
-can also send email directly to [email protected]. Please note that
+If you have a small patch to submit, please submit it via perlbug.  You
+can also send email directly to [email protected].  Please note that
 messages sent to perlbug may be held in a moderation queue, so you
 won't receive a response immediately.
 
 You'll know your submission has been processed when you receive an
-email from our ticket tracking system. This email will give you a
-ticket number. Once your patch has made it to the ticket tracking
+email from our ticket tracking system.  This email will give you a
+ticket number.  Once your patch has made it to the ticket tracking
 system, it will also be sent to the [email protected] list.
 
-Patches are reviewed and discussed on the p5p list. Simple,
+Patches are reviewed and discussed on the p5p list.  Simple,
 uncontroversial patches will usually be applied without any discussion.
 When the patch is applied, the ticket will be updated and you will
-receive email. In addition, an email will be sent to the p5p list.
+receive email.  In addition, an email will be sent to the p5p list.
 
-In other cases, the patch will need more work or discussion. That will
+In other cases, the patch will need more work or discussion.  That will
 happen on the p5p list.
 
 You are encouraged to participate in the discussion and advocate for
-your patch. Sometimes your patch may get lost in the shuffle. It's
+your patch.  Sometimes your patch may get lost in the shuffle.  It's
 appropriate to send a reminder email to p5p if no action has been taken
-in a month. Please remember that the Perl 5 developers are all
+in a month.  Please remember that the Perl 5 developers are all
 volunteers, and be polite.
 
 Changes are always applied directly to the main development branch,
-called "blead". Some patches may be backported to a maintenance branch.
+called "blead".  Some patches may be backported to a maintenance branch.
 If you think your patch is appropriate for the maintenance branch,
 please explain why when you submit it.
 
@@ -218,9 +218,9 @@ can do to help the Perl 5 Porters accept your patch.
 =head3 Patch style
 
 If you used git to check out the Perl source, then using C<git
-format-patch> will produce a patch in a style suitable for Perl. The
+format-patch> will produce a patch in a style suitable for Perl.  The
 C<format-patch> command produces one patch file for each commit you
-made. If you prefer to send a single patch for all commits, you can use
+made.  If you prefer to send a single patch for all commits, you can use
 C<git diff>.
 
   % git checkout blead
@@ -228,15 +228,15 @@ C<git diff>.
   % git diff blead my-branch-name
 
 This produces a patch based on the difference between blead and your
-current branch. It's important to make sure that blead is up to date
+current branch.  It's important to make sure that blead is up to date
 before producing the diff, that's why we call C<git pull> first.
 
-We strongly recommend that you use git if possible. It will make your
+We strongly recommend that you use git if possible.  It will make your
 life easier, and ours as well.
 
 However, if you're not using git, you can still produce a suitable
-patch. You'll need a pristine copy of the Perl source to diff against.
-The porters prefer unified diffs. Using GNU C<diff>, you can produce a
+patch.  You'll need a pristine copy of the Perl source to diff against.
+The porters prefer unified diffs.  Using GNU C<diff>, you can produce a
 diff like this:
 
   % diff -Npurd perl.pristine perl.mine
@@ -247,11 +247,11 @@ build artifacts, or you may get a confusing result.
 =head3 Commit message
 
 As you craft each patch you intend to submit to the Perl core, it's
-important to write a good commit message. This is especially important
+important to write a good commit message.  This is especially important
 if your submission will consist of a series of commits.
 
 The first line of the commit message should be a short description
-without a period. It should be no longer than the subject line of an
+without a period.  It should be no longer than the subject line of an
 email, 50 characters being a good rule of thumb.
 
 A lot of Git tools (Gitweb, GitHub, git log --pretty=oneline, ...) will
@@ -271,11 +271,11 @@ to Perl.
 =item * Why
 
 Your commit message should describe why the change you are making is
-important. When someone looks at your change in six months or six
+important.  When someone looks at your change in six months or six
 years, your intent should be clear.
 
 If you're deprecating a feature with the intent of later simplifying
-another bit of code, say so. If you're fixing a performance problem or
+another bit of code, say so.  If you're fixing a performance problem or
 adding a new feature to support some other bit of the core, mention
 that.
 
@@ -294,22 +294,22 @@ month or next year.
 =back
 
 A commit message isn't intended to take the place of comments in your
-code. Commit messages should describe the change you made, while code
+code.  Commit messages should describe the change you made, while code
 comments should describe the current state of the code.
 
 If you've just implemented a new feature, complete with doc, tests and
-well-commented code, a brief commit message will often suffice. If,
+well-commented code, a brief commit message will often suffice.  If,
 however, you've just changed a single character deep in the parser or
 lexer, you might need to write a small novel to ensure that future
 readers understand what you did and why you did it.
 
 =head3 Comments, Comments, Comments
 
-Be sure to adequately comment your code. While commenting every line is
+Be sure to adequately comment your code.  While commenting every line is
 unnecessary, anything that takes advantage of side effects of
 operators, that creates changes that will be felt outside of the
 function being patched, or that others may find confusing should be
-documented. If you are going to err, it is better to err on the side of
+documented.  If you are going to err, it is better to err on the side of
 adding too many comments than too few.
 
 The best comments explain I<why> the code does what it does, not I<what
@@ -402,7 +402,7 @@ often used by Perl aggregators, such as Linux distributors.
 
 If your patch changes code (rather than just changing documentation),
 you should also include one or more test cases which illustrate the bug
-you're fixing or validate the new functionality you're adding. In
+you're fixing or validate the new functionality you're adding.  In
 general, you should update an existing test file rather than create a
 new one.
 
@@ -413,7 +413,7 @@ Your test suite additions should generally follow these 
guidelines
 
 =item *
 
-Know what you're testing. Read the docs, and the source.
+Know what you're testing.  Read the docs, and the source.
 
 =item *
 
@@ -443,7 +443,7 @@ Give meaningful error messages when a test fails.
 
 =item *
 
-Avoid using qx// and system() unless you are testing for them. If you
+Avoid using qx// and system() unless you are testing for them.  If you
 do use them, make sure that you cover _all_ perl platforms.
 
 =item *
@@ -465,7 +465,7 @@ Add comments to the code explaining what you are testing 
for.
 
 =item *
 
-Make updating the '1..42' string unnecessary. Or make sure that you
+Make updating the '1..42' string unnecessary.  Or make sure that you
 update it.
 
 =item *
@@ -488,7 +488,7 @@ This works just like patching anything else, with one extra
 consideration.
 
 Modules in the F<cpan/> directory of the source tree are maintained
-outside of the Perl core. When the author updates the module, the
+outside of the Perl core.  When the author updates the module, the
 updates are simply copied into the core.  See that module's
 documentation or its listing on L<http://search.cpan.org/> for more
 information on reporting bugs and submitting patches.
@@ -508,7 +508,7 @@ core.
 
 For changes significant enough to warrant a F<pod/perldelta.pod> entry,
 the porters will greatly appreciate it if you submit a delta entry
-along with your actual change. Significant changes include, but are not
+along with your actual change.  Significant changes include, but are not
 limited to:
 
 =over 4
@@ -549,13 +549,13 @@ Important platform-specific changes
 =back
 
 Please make sure you add the perldelta entry to the right section
-within F<pod/perldelta.pod>. More information on how to write good
+within F<pod/perldelta.pod>.  More information on how to write good
 perldelta entries is available in the C<Style> section of
 F<Porting/how_to_write_a_perldelta.pod>.
 
 =head2 What makes for a good patch?
 
-New features and extensions to the language can be contentious. There
+New features and extensions to the language can be contentious.  There
 is no specific set of criteria which determine what features get added,
 but here are some questions to consider when developing a patch:
 
@@ -589,28 +589,28 @@ Either assimilate new technologies, or build bridges to 
them.
 
 =head3 Where is the implementation?
 
-All the talk in the world is useless without an implementation. In
+All the talk in the world is useless without an implementation.  In
 almost every case, the person or people who argue for a new feature
-will be expected to be the ones who implement it. Porters capable of
+will be expected to be the ones who implement it.  Porters capable of
 coding new features have their own agendas, and are not available to
 implement your (possibly good) idea.
 
 =head3 Backwards compatibility
 
-It's a cardinal sin to break existing Perl programs. New warnings can
+It's a cardinal sin to break existing Perl programs.  New warnings can
 be contentious--some say that a program that emits warnings is not
-broken, while others say it is. Adding keywords has the potential to
+broken, while others say it is.  Adding keywords has the potential to
 break programs, changing the meaning of existing token sequences or
 functions might break programs.
 
 The Perl 5 core includes mechanisms to help porters make backwards
 incompatible changes more compatible such as the L<feature> and
-L<deprecate> modules. Please use them when appropriate.
+L<deprecate> modules.  Please use them when appropriate.
 
 =head3 Could it be a module instead?
 
 Perl 5 has extension mechanisms, modules and XS, specifically to avoid
-the need to keep changing the Perl interpreter. You can write modules
+the need to keep changing the Perl interpreter.  You can write modules
 that export functions, you can give those functions prototypes so they
 can be called like built-in functions, you can even write XS code to
 mess with the runtime data structures of the Perl interpreter if you
@@ -633,26 +633,26 @@ potential to introduce new bugs.
 
 =head3 How big is it?
 
-The smaller and more localized the change, the better. Similarly, a
+The smaller and more localized the change, the better.  Similarly, a
 series of small patches is greatly preferred over a single large patch.
 
 =head3 Does it preclude other desirable features?
 
 A patch is likely to be rejected if it closes off future avenues of
-development. For instance, a patch that placed a true and final
+development.  For instance, a patch that placed a true and final
 interpretation on prototypes is likely to be rejected because there are
 still options for the future of prototypes that haven't been addressed.
 
 =head3 Is the implementation robust?
 
 Good patches (tight code, complete, correct) stand more chance of going
-in. Sloppy or incorrect patches might be placed on the back burner
+in.  Sloppy or incorrect patches might be placed on the back burner
 until the pumpking has time to fix, or might be discarded altogether
 without further notice.
 
 =head3 Is the implementation generic enough to be portable?
 
-The worst patches make use of system-specific features. It's highly
+The worst patches make use of system-specific features.  It's highly
 unlikely that non-portable additions to the Perl language will be
 accepted.
 
@@ -671,14 +671,14 @@ patch won't be accidentally thrown away by someone in the 
future?
 =head3 Is there enough documentation?
 
 Patches without documentation are probably ill-thought out or
-incomplete. No features can be added or changed without documentation,
+incomplete.  No features can be added or changed without documentation,
 so submitting a patch for the appropriate pod docs as well as the
 source code is important.
 
 =head3 Is there another way to do it?
 
 Larry said "Although the Perl Slogan is I<There's More Than One Way to
-Do It>, I hesitate to make 10 ways to do something". This is a tricky
+Do It>, I hesitate to make 10 ways to do something".  This is a tricky
 heuristic to navigate, though--one man's essential addition is another
 man's pointless cruft.
 
@@ -689,10 +689,10 @@ authors, ... Perl is supposed to be easy.
 
 =head3 Patches speak louder than words
 
-Working code is always preferred to pie-in-the-sky ideas. A patch to
+Working code is always preferred to pie-in-the-sky ideas.  A patch to
 add a feature stands a much higher chance of making it to the language
 than does a random feature request, no matter how fervently argued the
-request might be. This ties into "Will it be useful?", as the fact that
+request might be.  This ties into "Will it be useful?", as the fact that
 someone took the time to make the patch demonstrates a strong desire
 for the feature.
 
@@ -702,10 +702,10 @@ The core uses the same testing style as the rest of Perl, 
a simple
 "ok/not ok" run through Test::Harness, but there are a few special
 considerations.
 
-There are three ways to write a test in the core. L<Test::More>,
-F<t/test.pl> and ad hoc C<print $test ? "ok 42\n" : "not ok 42\n">. The
+There are three ways to write a test in the core: L<Test::More>,
+F<t/test.pl> and ad hoc C<print $test ? "ok 42\n" : "not ok 42\n">.  The
 decision of which to use depends on what part of the test suite you're
-working on. This is a measure to prevent a high-level failure (such as
+working on.  This is a measure to prevent a high-level failure (such as
 Config.pm breaking) from causing basic functionality tests to fail.
 
 The F<t/test.pl> library provides some of the features of
@@ -720,7 +720,7 @@ Protocol|http://testanything.org>.
 =item * F<t/base>, F<t/comp> and F<t/opbasic>
 
 Since we don't know if require works, or even subroutines, use ad hoc
-tests for these three. Step carefully to avoid using the feature being
+tests for these three.  Step carefully to avoid using the feature being
 tested.  Tests in F<t/opbasic>, for instance, have been placed there rather
 than in F<t/op> because they test functionality which F<t/test.pl> presumes
 has already been demonstrated to work.
@@ -736,25 +736,25 @@ sure to skip the test gracefully if it's not there.
 =item * Everything else
 
 Now that the core of Perl is tested, L<Test::More> can and should be
-used. You can also use the full suite of core modules in the tests.
+used.  You can also use the full suite of core modules in the tests.
 
 =back
 
 When you say "make test", Perl uses the F<t/TEST> program to run the
-test suite (except under Win32 where it uses F<t/harness> instead). All
+test suite (except under Win32 where it uses F<t/harness> instead).  All
 tests are run from the F<t/> directory, B<not> the directory which
-contains the test. This causes some problems with the tests in F<lib/>,
+contains the test.  This causes some problems with the tests in F<lib/>,
 so here's some opportunity for some patching.
 
-You must be triply conscious of cross-platform concerns. This usually
+You must be triply conscious of cross-platform concerns.  This usually
 boils down to using L<File::Spec> and avoiding things like C<fork()>
 and C<system()> unless absolutely necessary.
 
 =head2 Special C<make test> targets
 
 There are various special make targets that can be used to test Perl
-slightly differently than the standard "test" target. Not all them are
-expected to give a 100% success rate. Many of them have several
+slightly differently than the standard "test" target.  Not all them are
+expected to give a 100% success rate.  Many of them have several
 aliases, and many of them are not available on certain operating
 systems.
 
@@ -773,16 +773,16 @@ F<t/op>, F<t/uni> and F<t/mro> tests.
 =item * test.valgrind check.valgrind
 
 (Only in Linux) Run all the tests using the memory leak + naughty
-memory access tool "valgrind". The log files will be named
+memory access tool "valgrind".  The log files will be named
 F<testname.valgrind>.
 
 =item * test_harness
 
 Run the test suite with the F<t/harness> controlling program, instead
-of F<t/TEST>. F<t/harness> is more sophisticated, and uses the
+of F<t/TEST>.  F<t/harness> is more sophisticated, and uses the
 L<Test::Harness> module, thus using this test target supposes that perl
-mostly works. The main advantage for our purposes is that it prints a
-detailed summary of failed tests at the end. Also, unlike F<t/TEST>, it
+mostly works.  The main advantage for our purposes is that it prints a
+detailed summary of failed tests at the end.  Also, unlike F<t/TEST>, it
 doesn't redirect stderr to stdout.
 
 Note that under Win32 F<t/harness> is always used instead of F<t/TEST>,
@@ -790,7 +790,7 @@ so there is no special "test_harness" target.
 
 Under Win32's "test" target you may use the TEST_SWITCHES and
 TEST_FILES environment variables to control the behaviour of
-F<t/harness>. This means you can say
+F<t/harness>.  This means you can say
 
     nmake test TEST_FILES="op/*.t"
     nmake test TEST_SWITCHES="-torture" TEST_FILES="op/*.t"
@@ -804,9 +804,9 @@ Sets PERL_SKIP_TTY_TEST to true before running normal test.
 =head2 Parallel tests
 
 The core distribution can now run its regression tests in parallel on
-Unix-like platforms. Instead of running C<make test>, set C<TEST_JOBS>
+Unix-like platforms.  Instead of running C<make test>, set C<TEST_JOBS>
 in your environment to the number of tests to run in parallel, and run
-C<make test_harness>. On a Bourne-like shell, this can be done as
+C<make test_harness>.  On a Bourne-like shell, this can be done as
 
     TEST_JOBS=3 make test_harness  # Run 3 tests in parallel
 
@@ -816,7 +816,7 @@ non-conflicting test scripts itself, and there is no 
standard interface
 to C<make> utilities to interact with their job schedulers.
 
 Note that currently some test scripts may fail when run in parallel
-(most notably F<ext/IO/t/io_dir.t>). If necessary, run just the failing
+(most notably F<ext/IO/t/io_dir.t>).  If necessary, run just the failing
 scripts again sequentially and see if the failures go away.
 
 =head2 Running tests by hand
@@ -835,14 +835,14 @@ or
 =head2 Using F<t/harness> for testing
 
 If you use C<harness> for testing, you have several command line
-options available to you. The arguments are as follows, and are in the
+options available to you.  The arguments are as follows, and are in the
 order that they must appear if used together.
 
     harness -v -torture -re=pattern LIST OF FILES TO TEST
     harness -v -torture -re LIST OF PATTERNS TO MATCH
 
 If C<LIST OF FILES TO TEST> is omitted, the file list is obtained from
-the manifest. The file list may include shell wildcards which will be
+the manifest.  The file list may include shell wildcards which will be
 expanded out.
 
 =over 4
@@ -858,14 +858,14 @@ Run the torture tests as well as the normal set.
 
 =item * -re=PATTERN
 
-Filter the file list so that all the test files run match PATTERN. Note
+Filter the file list so that all the test files run match PATTERN.  Note
 that this form is distinct from the B<-re LIST OF PATTERNS> form below
 in that it allows the file list to be provided as well.
 
 =item * -re LIST OF PATTERNS
 
 Filter the file list so that all the test files run match
-/(LIST|OF|PATTERNS)/. Note that with this form the patterns are joined
+/(LIST|OF|PATTERNS)/.  Note that with this form the patterns are joined
 by '|' and you cannot supply a list of files, instead the test files
 are obtained from the MANIFEST.
 
@@ -883,7 +883,7 @@ affect the execution of the test:
 =item * PERL_CORE=1
 
 indicates that we're running this test as part of the perl core test
-suite. This is useful for modules that have a dual life on CPAN.
+suite.  This is useful for modules that have a dual life on CPAN.
 
 =item * PERL_DESTRUCT_LEVEL=2
 
@@ -898,7 +898,7 @@ F<./perl>).
 
 =item * PERL_SKIP_TTY_TEST
 
-if set, tells to skip the tests that need a terminal. It's actually set
+if set, tells to skip the tests that need a terminal.  It's actually set
 automatically by the Makefile, but can also be forced artificially by
 running 'make test_notty'.
 
@@ -911,7 +911,7 @@ running 'make test_notty'.
 =item * PERL_TEST_Net_Ping
 
 Setting this variable runs all the Net::Ping modules tests, otherwise
-some tests that interact with the outside world are skipped. See
+some tests that interact with the outside world are skipped.  See
 L<perl58delta>.
 
 =item * PERL_TEST_NOVREXX
@@ -942,7 +942,7 @@ To hack on the Perl guts, you'll need to read the following 
things:
 
 =item * L<perlsource>
 
-An overview of the Perl source tree. This will help you find the files
+An overview of the Perl source tree.  This will help you find the files
 you're looking for.
 
 =item * L<perlinterp>
@@ -953,12 +953,12 @@ Perl does what it does.
 =item * L<perlhacktut>
 
 This document walks through the creation of a small patch to Perl's C
-code. If you're just getting started with Perl core hacking, this will
+code.  If you're just getting started with Perl core hacking, this will
 help you understand how it works.
 
 =item * L<perlhacktips>
 
-More details on hacking the Perl core. This document focuses on lower
+More details on hacking the Perl core.  This document focuses on lower
 level details such as how to write tests, compilation issues,
 portability, debugging, etc.
 
@@ -967,7 +967,7 @@ If you plan on doing serious C hacking, make sure to read 
this.
 =item * L<perlguts>
 
 This is of paramount importance, since it's the documentation of what
-goes where in the Perl source. Read it over a couple of times and it
+goes where in the Perl source.  Read it over a couple of times and it
 might start to make sense - don't worry if it doesn't yet, because the
 best way to study it is to read it in conjunction with poking at Perl
 source, and we'll do that later on.
@@ -981,7 +981,7 @@ L<http://search.cpan.org/dist/illguts/>
 
 A working knowledge of XSUB programming is incredibly useful for core
 hacking; XSUBs use techniques drawn from the PP code, the portion of
-the guts that actually executes a Perl program. It's a lot gentler to
+the guts that actually executes a Perl program.  It's a lot gentler to
 learn those techniques from simple examples and explanation than from
 the core itself.
 
@@ -1008,9 +1008,9 @@ http://www.nntp.perl.org/group/perl.daily-build.reports/ )
 automatically test Perl source releases on platforms with various
 configurations.
 
-Both efforts welcome volunteers. In order to get involved in smoke
+Both efforts welcome volunteers.  In order to get involved in smoke
 testing of the perl itself visit
-L<http://search.cpan.org/dist/Test-Smoke/>. In order to start smoke
+L<http://search.cpan.org/dist/Test-Smoke/>.  In order to start smoke
 testing CPAN modules visit
 L<http://search.cpan.org/dist/CPANPLUS-YACSmoke/> or
 L<http://search.cpan.org/dist/minismokebox/> or
@@ -1034,14 +1034,14 @@ who knows, you may unearth a bug in the patch...
 =item *
 
 Do read the README associated with your operating system, e.g.
-README.aix on the IBM AIX OS. Don't hesitate to supply patches to that
+README.aix on the IBM AIX OS.  Don't hesitate to supply patches to that
 README if you find anything missing or changed over a new OS release.
 
 =item *
 
 Find an area of Perl that seems interesting to you, and see if you can
-work out how it works. Scan through the source, and step over it in the
-debugger. Play, poke, investigate, fiddle! You'll probably get to
+work out how it works.  Scan through the source, and step over it in the
+debugger.  Play, poke, investigate, fiddle! You'll probably get to
 understand not just your chosen area but a much wider range of
 F<perl>'s activity as well, and probably sooner than you'd think.
 
@@ -1050,7 +1050,7 @@ F<perl>'s activity as well, and probably sooner than 
you'd think.
 =head2 "The Road goes ever on and on, down from the door where it began."
 
 If you can do these things, you've started on the long road to Perl
-porting. Thanks for wanting to help make Perl better - and happy
+porting.  Thanks for wanting to help make Perl better - and happy
 hacking!
 
 =head2 Metaphoric Quotations
@@ -1058,7 +1058,7 @@ hacking!
 If you recognized the quote about the Road above, you're in luck.
 
 Most software projects begin each file with a literal description of
-each file's purpose. Perl instead begins each with a literary allusion
+each file's purpose.  Perl instead begins each with a literary allusion
 to that file's purpose.
 
 Like chapters in many books, all top-level Perl source files (along
@@ -1067,20 +1067,20 @@ inscription that alludes, indirectly and 
metaphorically, to the
 material you're about to read.
 
 Quotations are taken from writings of J.R.R. Tolkien pertaining to his
-Legendarium, almost always from I<The Lord of the Rings>. Chapters and
+Legendarium, almost always from I<The Lord of the Rings>.  Chapters and
 page numbers are given using the following editions:
 
 =over 4
 
 =item *
 
-I<The Hobbit>, by J.R.R. Tolkien. The hardcover, 70th-anniversary
+I<The Hobbit>, by J.R.R. Tolkien.  The hardcover, 70th-anniversary
 edition of 2007 was used, published in the UK by Harper Collins
 Publishers and in the US by the Houghton Mifflin Company.
 
 =item *
 
-I<The Lord of the Rings>, by J.R.R. Tolkien. The hardcover,
+I<The Lord of the Rings>, by J.R.R. Tolkien.  The hardcover,
 50th-anniversary edition of 2004 was used, published in the UK by
 Harper Collins Publishers and in the US by the Houghton Mifflin
 Company.
@@ -1089,7 +1089,7 @@ Company.
 
 I<The Lays of Beleriand>, by J.R.R. Tolkien and published posthumously
 by his son and literary executor, C.J.R. Tolkien, being the 3rd of the
-12 volumes in Christopher's mammoth I<History of Middle Earth>. Page
+12 volumes in Christopher's mammoth I<History of Middle Earth>.  Page
 numbers derive from the hardcover edition, first published in 1983 by
 George Allen & Unwin; no page numbers changed for the special 3-volume
 omnibus edition of 2002 or the various trade-paper editions, all again
@@ -1100,7 +1100,7 @@ now by Harper Collins or Houghton Mifflin.
 Other JRRT books fair game for quotes would thus include I<The
 Adventures of Tom Bombadil>, I<The Silmarillion>, I<Unfinished Tales>,
 and I<The Tale of the Children of Hurin>, all but the first
-posthumously assembled by CJRT. But I<The Lord of the Rings> itself is
+posthumously assembled by CJRT.  But I<The Lord of the Rings> itself is
 perfectly fine and probably best to quote from, provided you can find a
 suitable quote there.
 
@@ -1108,7 +1108,7 @@ So if you were to supply a new, complete, top-level 
source file to add
 to Perl, you should conform to this peculiar practice by yourself
 selecting an appropriate quotation from Tolkien, retaining the original
 spelling and punctuation and using the same format the rest of the
-quotes are in. Indirect and oblique is just fine; remember, it's a
+quotes are in.  Indirect and oblique is just fine; remember, it's a
 metaphor, so being meta is, after all, what it's for.
 
 =head1 AUTHOR

--
Perl5 Master Repository

Reply via email to