Localization/lang-ko
국제화 기술은 귀하의 국가에서 말해지고, 가르치고, 이용되는 언어를 표현하고 작문하기 위한 기술입니다. 지역화는 지역적 이용을 위한 소프트웨어 또는 컨텐트를 선택하는 과정입니다.
지역화는 폰트, 스크립트 레이아웃, 인풋 방식, 스피치 합성, 음악, collating order, 숫자 및 날짜 포맷, 사전, 그리고 스펠링 검사기 등이 대표적입니다.
리눅스는 마이크로소프트 윈도우보다 지역화가 훨씬 광범위하게 진행되었는데, 어떤 벤더의 도움도 요구되지 않기 때문입니다; 자유 소프트웨어와 컨텐트 공동체 간의 협력을 통해 중복 업무를 줄이는 것이 매우 중요합니다.
문제의 큽니다. Ethnologue에는 세계의 각종 언어에 대한 광범위한 정보가 있습니다.
- Wikipedia's definition도 참조하십시오.
이 페이지는 지역화의 핵심 주제와 툴들, 그리고 이슈를 개괄적으로 다룹니다.
기본적인 지역화 주제
문자 세트
유니코드는 자유 소프트웨어에서 이용되는 "현대" 어플리케이션과 툴킷에서 완전히 지원됩니다. Legacy 문자 세트 역시 존재하지만, 근래의 어플리케이션들은 유니코드를 이용합니다.
Collation order (텍스트가 리눅스에 의해 소트될 때, 소팅 순서)는 C 라이버러리에서 일반적으로 잘 지원됩니다.
- See also: Category:Fonts, Unicode.
스크립트 레이아웃
OLPC는 Pango library를 주로 사용하는데, 대부분의 "hard" 언어들 레이아웃이 가능합니다; 아랍어, 인도어, 해브루, 페르시안, 태국 등. 이 라이버러리는 modular puggable 레이아웃 엔진을 가지며, bi-directional 레이아웃은 물론 버티컬 텍스트도 지원합니다. 전반적으로, 일부 이슈들이 남아있지만, 팡고는 매우 뛰어나며 대부분의 스크립트들을 다룰 수 있습니다.
- See also: Category:Languages (international)
폰트
컨텐트를 공유하고, 문화적 유산을 보존하기 위해서, OLPC의 목표는 모든 국가들의 언어로 번역되어야 합니다. 리눅스는 Fontconfig을 사용함으로써, 다른 운영 시스테보다 우수한 폰트 개념을 가집니다. 이 시스템은 폰트 시스템을 구성하고, 일련의 언어들을 포괄하기 위해 요구되는 폰트 세트를 정의하는데 사용됩니다.
리눅스에서 이용되는 폰트 포맷은 OpenType, TrueType 등을 포함합니다: Freetype 참조. 현재 프리타입에 의해 지원되는 폰트 포맷 대부분은 구식이며, 최적의 스크린은 오픈타입 및 트루타입 포맷 폰트로 얻어집니다. Type 1 fonts는 인쇄 목적에 주로 적합하며; 오늘날 프리타입의 타입 1 폰트 렌더러는 썩 좋지가 않습니다.타입 1은 저해상도 스크린에서 프로그래밍 가능한 힌팅 programmatic hinting을 지원하지 않습니다.
OLPC는 상대적으로 고해상도 스크린을 가집니다; 특히 200DPI 흑백모드에서 탁월합니다.
프리 폰트
프리폰트는 대부분의 스크립트에 가용하지만, 일부 폰트는 라이선스가 필요합니다. Free fonts are available for most scripts in the world, though some fonts are licensed incorrectly for completely free redistribution.
스크린 폰트의 필요성
XO의 해상도와 관계없이, 우리는 우리의 어플리케이션과 컨텐트가 다른 스크린에서도 가용하길 바라므로, 고품질 스크린 폰트의 범주를 넓힐 필요가 있습니다. "DejaVu" font family (derived from Bitstream Vera)는 대부분의 Latin alphabets과 일부 언어를 지원합니다. 이 훼밀리는 스크린 용도에서 일반적으로 좋은 "힌팅 hinting"을 가집니다. SIL International은 또한 추가적인 지역 언어를 위한 폰트를 구성하고 있습니다. also builds fonts for a number of additional languages of local interest.
이러한 활동에 참여해 주시길 바랍니다. hinting glyphs은 따분하지만, 매우 중요한 작업이며, 기부와 판매 buyouts 역시 기대하고 있습니다.
키보드
OLPC Keyboard layouts document OLPC's currently available keyboard layouts: further layouts are a modest amount of work, requiring people with local expertise to work with OLPC staff to generate new layouts.
- See also: Category:Keyboard, HIG-Input Systems-Keyboard
인풋 방식
An input method is software that allows typing of complex characters, for example for languages such as Chinese, Japanese, Korean. Some issues remain, for example: Arabic ligatures, by avoiding putting them on the keyboard we've avoided the need for an input method. However, such workarounds may not be feasible for your language.
Free software systems now are using SCIM - Smart Common Input Method Platform. SCIM is replacing older input method systems.
We need to know what languages are taught as “foreign” languages, as well as are native, to design keyboards that are most useful in each country. For example, the Nigerian keyboard is designed to allow easy entry of English, Hausa, and Yoruba, which are common languages in much of Nigeria. The "US/International" covers most of the western European languages.
- See also: Input methods, [[HIG-Input Systems
Accessibility and Usability
스피치 합성
There are tradeoffs of size vs. fidelity vs. effort to synthesize a new language between the speech synthesis software that is available, which includes festival, flite, espeak are available.
Espeak is small enough for us to often bundle and covers quite a few languages: ~10 languages currently supported tuned by native speakers with 10 more languages underway.
Synthesis is essential or accessibility to content by people with vision problems, and will need to be integrated with the ATK library used, as well as literacy training, other uses as part of a GUI. Full localization therefore involves selection of a suitable synthesis system and integration into the ATK framework, along with localization of that system for the particular language involved.
Speech synthesis is usually not a good guide for pronunciation learning languages – but it may be better than a poor teacher who has never had the opportunity to learn from a native speaker of that language.
- See also Category:Accessibility
뮤직과 사운드 샘플
We want much more than dead white male western instruments for dead white male composers!
Clean samples of your musical instruments and music needed!
Samples need appropriate licensing terms.
- See also TamTam: Sounds
사전, 스펠링 체커, Thesaurus
Support exists for most major languages.
Spelling, Hyphenation, Thesaurus dictionaries may be needed for different parts of Linux, which may or may not apply to OLPC directly; for example you can check:
Of these, the first three are most immediately interesting to OLPC.
문자 인식
Stroke/character recognizer localization is of some interest with the pen/tablet: in the future (Gen 2) when we have a touch screen they will become essential. xstroke is one such individual character/stroke recognizer, sufficient for alphabets of up to about 100 characters.
고려사항
현재의 단점들
There are some real shortcomings where help is needed. These include:
- Non-Gregorian calendars
- Non-Latin digits (Roozbeh Pournader has patches, but these are not yet integrated and may need help).
- and the sheer scale of the localization problem will eventually require changes in free software projects.
지역화 기술
It only takes a small team to localize Linux for a language: e.g. Welsh, Icelandic, which are relatively small languages, have been pretty fully localized by small teams.
You can do the work yourself, hire the work out, or find volunteers among universities (worldwide), the world wide internet and free software community. Add to existing projects whenever possible. By checking with some of the major free software projects (e.g. Gnome, OpenOffice, Mozilla, KDE), you can often locate people already at work in your language.
Work directly in the software and content projects whenever possible. This makes your work available worldwide, while lessens the ongoing work. If you keep your localization work local, others cannot benefit from your work and effort and your software and content will be that much harder to localize.
툴
Some example tools include pootle, kbabel and rosetta. Most software uses the GNU “gettext” libraries and standard .po files, including Sugar; Firefox and OpenOffice have their own systems for historical reasons. Wordforge is a good place to get plugged into tools and the community efforts.
The cldr project is worth watching, though OpenOffice is the first major project using this.
Remember, contribute your translations to the “upstream” projects to minimize long term effort: share your work with the world. Do not presume that if one Linux distribution has your effort that you are finished; some Linux distributions are not good about working with the community that builds and distributes the original software.
라이선싱
Translated strings will often be useful among many projects, not just the the project you are working on translating, therefore, since the MIT/BSD (3 clause) licenses are usable by all projects, these are the safest licenses to use for translation to enable widest sharing.
The SIL OFL license recommended for Fonts. An often overlooked issue with fonts is that they are incorporated into documents themselves (for example, into PDF documents) and that therefore licensing needs to be considered carefully.
- See also Software licensing
다음 단계
Localization is by nature local: but languages often crosses borders. Please contact Jim Gettys to identify issues.
We need identified people/organizations responsible for language, translation, keyboards, speech synthesis, an effective free software community leaders to help with local deployment and "on the ground" knowledge.
슈가 로컬리제이션
Sugar and sugar applications use standard .po files, and can be localized using the usual tools.
일반적인 리눅스 로컬리제이션
By looking at the gnome, mozilla, OpenOffice, KDE projects, you can get plugged into translating other Linux software of general interest.
현재의 l10n 프로젝트들
라이버러리 익스체인지
- Library strings -- header and descriptive strings for an OLPC sample library. Includes some PO-like strings for the following sections:
- Localization/www.laptop.org -- The l10n effort for the new www.laptop.org website
- We can't translate everything, but we sure want to hear what you would like to see translated into your language. If you got a translation to suggest please let us know!
액티비티
Add / include links to upstream localization where appropriate.
- camera — en | es | ko | pt | zh-CN
- web?
- read?
- write?
- blockparty?
- See also
- Translators & Translating for the localization of this wiki.
국가 그룹들
- Albania
- Argentina
- Austria
- Brazil
- China
- Colombia
- Egypt
- Ethiopia
- Spain
- France
- Germany
- Greece
- India
- Kenya
- 한국 (S.Korea)
- 조선 (N.Korea)
- Laos
- Libya
- Nepal
- Nigeria
- Poland
- Romania
- Russia
- South Africa
- Sri Lanka
- Thailand
- Uruguay
한국어를 사용하는 국가 또는 공동체
People using Korean as their native language are those in South Korea (한국인) and North Korea (조선인). Some Chinese and those with other nationalities, living in the Nothern part of Korea also are using Korean as their second language, because of some historical issues. They are called as 고려인(Korea-in) and 조선족 (Chosun-zok or Korean Chinese) respectively.
Currently OLPC Korea (or XO Korea) is covering all those nations and regions. In a near future, we hope there will be regional XO groups for those.