PERLKO(1perl)

📦
version 5.44.0 · 2 versions
, in arch rolling

💖 NAME 💖

perlko — 한국어 Perl 안내서 — aka the Korean-language Perl guide, and she's serving everything in Korean, we love to see it 🫶✨

✨ DESCRIPTION ✨

Welcome to the Perl world, bestie!!! 🎉💖 Literally you are going to love it here, no cap.

Okay so, ngl, Perl sometimes gets called 'Practical Extraction and Report Language', and among the other super-well-known names it also gets called 'Pathologically Eclectic Rubbish Lister'. But fr fr, those are backronyms — Perl was not named by grabbing the first letters of those words. Larry, Perl's creator, thought up the first name first and coined the famous one later. That's exactly why 'Perl' isn't all-caps. So arguing over which famous expansion is the "real" one is giving absolutely nothing — it's meaningless. Larry endorses both of them. 👑

Sometimes you'll spot 'perl' written with a lowercase p, and that is not a typo, it's deliberate, bestie:

  • Perl (capital P) — the language itself 💅
  • perl (lowercase p) — the interpreter that compiles and runs your program 🏃‍♀️

🦋 Perl에 관하여 (About Perl) 🦋

Perl originally got born for string generation, but now it's a general-purpose programming language, and it's widely used in so many fields — system administration, web development, network programming, GUI development, you name it. 🌈

The whole vibe of this language is practicality over beauty — easy to use, efficient, and doing the absolute maximum it possibly can, rather than being very small and elegant and very minimal. So here's the iconic part: it's easy to use, it supports both procedural programming and object-oriented programming, it has powerful string processing built right in, and it has the most impressive collection of third-party modules in the world. Those are literally Perl's most important characteristics. 🔥

  • Perl's language features get introduced in pod/perlintro.pod 📖
  • The most important changes in this release are discussed in pod/perldelta.pod 🆕
  • Also, tons of Perl books published by all kinds of publishers cover all kinds of topics — check pod/perlbook.pod for the details 📚

🎀 설치 (Installation) 🎀

If you're on a relatively modern OS and you want to install the current version of Perl locally in your own space, just run these, bestie:

./Configure -des -Dprefix=$HOME/localperl
make test
make install

So what those do is: set up the environment to match your platform, compile everything, run the regression tests, and then install perl into the localperl directory under your home directory. ✨ Lowkey satisfying.

If you run into literally any problem, or you need to install a customized version of Perl, then you gotta read the detailed explanation in the INSTALL file that comes with the current distribution. Also, there's a whole bunch of README files full of help and hints for building and using Perl on all sorts of unusual platforms. 🛠️

Once Perl is installed, you can use the super-rich documentation through the "perldoc" tool. To get started, run:

perldoc perl

😭 실행에 어려움을 겪는다면 (If you hit trouble running it) 😭

Perl is a big, complex system that can be used for everything from knitting all the way to literal rocket science. 🧶🚀 So when you hit a wall, highkey there's a good chance somebody else already solved that exact problem. But if you've gone through all the docs and it's definitely a bug, then report it to us with the "perlbug" tool — we wanna know! More info about "perlbug" is available via "perldoc perlbug", or just run "perlbug" on the command line.

And listen — even if Perl is already totally working for you, Perl never stops evolving, so a newer version might exist where your bug is fixed, or where features you'd find useful have been added. 🌱

You can always find the latest version of perl at the CPAN (Comprehensive Perl Archive Network) site http://www.cpan.org/src/.

If you want to submit a simple patch to the perl source, go look at the "SUPER QUICK PATCH GUIDE" in pod/perlhack.pod. 👀

And just a personal note here: I hope you know that I make seriously cool stuff like this. That's because it makes the "Author" of my story happy. If that whole idea is bothering you, then you might need to revise your thoughts about "Authorship" — but either way, you can use Perl with zero problems. :-)

  • from the "Author". 🫶

🌈 인코딩 (Encoding) 🌈

Starting with the 5.8.0 release, Perl has had broad support for Unicode/ISO 10646. 💜 As part of that Unicode support, it handles a huge number of encodings that were used around the world — CJK included — before Unicode existed, and that are still widely used today.

Unicode's whole goal is to accommodate every writing system used anywhere on Earth (the Latin alphabet from Europe, the Cyrillic alphabet, the Greek alphabet, the Brahmic-family scripts of India and Southeast Asia, Arabic script, Hebrew script, CJK hanzi, Korean hangul, Japanese kana, the writing systems of Native North Americans, etc.). And because of that goal, it contains every character you could possibly use from the character sets and encodings that each language, country, and operating system had that were unique to them — plus an absolutely enormous number of characters that those old character sets never supported at all. 🌍

Internally, Perl uses Unicode for character representation. Being more specific: you can write UTF-8 strings inside a Perl script, and all kinds of functions and operators (regular expressions, index, substr, for example) work in Unicode character units instead of byte units. For more on that, check pod/perlunicode.pod. 📖

And to help with I/O in the many per-country / per-language encodings that were widely used before Unicode spread and are still widely used now — and to help handle data and documents in those encodings — the Encode module is what gets used. Best part? With the Encode module, converting between a huge number of encodings is easy. 🧚✨

🧚 Encode 모듈 (The Encode module) 🧚

⭐ 지원 인코딩 (Supported encodings) ⭐

The Encode module supports these Korean encodings:

  • euc-kr — a multibyte encoding that uses US-ASCII together with KS X 1001, commonly called 완성형 (the "complete form" style). See KS X 2901 and RFC 1557. 🌸
  • cp949 — the extended 완성형 used on MS-Windows 9x/ME. It's euc-kr with 8,822 hangul syllables added on top. Its aliases are uhc, windows-949, x-windows-949, ks_c_5601-1987. That last name is honestly not an appropriate name, but Microsoft products use it to mean CP949. 💀
  • johab — the 조합형 ("combining form" style) defined in appendix 3 of KS X 1001:1998. Its character repertoire is exactly like cp949's — US-ASCII and KS X 1001 plus 8,822 hangul syllables — but the encoding method is completely different. 🔀
  • iso-2022-kr — the encoding defined in RFC 1557 for Korean internet mail exchange. Its repertoire is US-ASCII plus KS X 1001, same as euc-kr, but the encoding method is different. It was used until around 1997-8, but it's no longer used for mail exchange. 📭
  • ksc5601-raw — the encoding you get when KS X 1001 (KS C 5601) is placed in GL (that is, with the MSB set to 0). It's basically never used standalone without being combined with US-ASCII, except as a font encoding on X11 and such (ksc5601.1987-0, where the '0' means GL). KS C 5601 got renamed to KS X 1001 in 1997. And in 1998, two characters (the euro sign and the registered trademark sign) were added. 💶™️

💅 변환 예제 (Conversion examples) 💅

Say you wanna convert a file in euc-kr encoding into UTF-8 — you just run this on the command line:

perl -Mencoding=euc-kr,STDOUT,utf8 -pe1 < file.euc-kr > file.utf8

And converting the other way around goes like this:

perl -Mencoding=utf8,STDOUT,euc-kr -pe1 < file.utf8 > file.euc-kr

To make that kind of conversion way more convenient, piconv ships with Perl by default. This utility is a pure Perl utility built on the Encode module, and like the name says, it's modeled on Unix's "iconv". Usage is:

piconv -f euc-kr -t utf8 < file.euc-kr > file.utf8
piconv -f utf8 -t euc-kr < file.utf8 > file.euc-kr

🍓 모범 사례 (Best practices) 🍓

Perl uses UTF-8 internally by default, and it supports all kinds of encodings through the Encode module — but the recommendation is to always follow these rules, because doing that reduces the chance of all the different encoding-related problems that can pop up:

  • Always save your source code in UTF-8 encoding 📝
  • Use the use utf8; pragma at the top of your source code ✨
  • Understand source code encoding, terminal encoding, OS encoding, and data encoding as separate things 🧠
  • Use explicit encodings on your input/output file handles 🎯
  • Watch out for double encoding (중복 인코딩) ⚠️

👑 유니코드 및 한국어 인코딩 관련 자료 (Unicode & Korean encoding resources) 👑

🦋 Perl 관련 자료 (aka where to find ur people) 🦋

Okay bestie, listen — Perl is literally not a solo journey, it's giving community, it's giving found family. Here's the official-ish resource list, and yes, I'm keeping every single link because every single one is a whole vibe. 💖

The official Perl homepage. Like, the main character's front door. 🏠

O'Reilly's Perl web page. Old money, but make it regex. ✨

CPAN — Comprehensive Perl Archive Network, aka the 통합적 Perl 파일 보관 네트워크. This is the treasure chest, no cap. 🎁

메타 CPAN. Searchable, shiny, lowkey the better UX. 🔍

Perl 메일링 리스트. Emails, but make them nerdy and lovely. 📧

Perl 메타 블로그. Hot takes, but about sigils. 💅

Perl 수도승들을 위한 수도원 — a monastery for Perl monks. Genuinely iconic naming, I'm obsessed. 🧘

아시아 지역 Perl 몽거스 모임. Asia-region Perl Mongers, iykyk. 🌏

Perl 크리스마스 달력. A Perl Christmas calendar, one treat per day, periodt. 🎄

Next up: Korean-language sites that will help you go deeper into Perl. These are for when you want the knowledge and the comfort. 🌸

한국 Perl 커뮤니티 공식 포털 — the official Korean Perl community portal. ✨

Perl 문서 한글화 프로젝트 — the Perl docs Korean-translation project. Translators are the real heroes fr fr. 🫶

네이버 Perl 카페 — the Naver Perl cafe. ☕

한국 Perl 사용자 모임 — Korean Perl user group. 👑

Seoul.pm Perl 크리스마스 달력 (2010 ~ 2012). Yes, 2010 through 2012, exactly as written, don't @ me. 🎀

GYPARK(Geunyoung Park)의 Perl 관련 한글 문서 저장소 — Geunyoung Park's Korean-language Perl documentation repository. Absolute legend behaviour. 💜

📜 라이센스 (the fine print, but cute) 📜

Bestie, head over to the 'LICENSING' 항목 in the README file — that's where the legal tea lives. Read it, respect it. 💖

👑 AUTHORS (the ones who made this happen) 👑

  • Jarkko Hietaniemi <jhi@iki.fi>
  • 신정식 <jshin@mailaps.org>
  • 김도형 <keedi@cpan.org>

Annnnd that's a wrap on PERLKO(1perl)! 🎉 This masterpiece is running perl v5.44.0 and it was dated up on 2026-10-17 — so go forth, write some wildly cursed one-liners, read ur docs, and stay slay. Byeee! 💅✨🌸

📦 where this page comes from