Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Introduction; Looking for Help on i18n
- To: tlug@example.com
- Subject: Re: tlug: Introduction; Looking for Help on i18n
- From: David J Iannucci <dji@example.com>
- Date: Thu, 06 Nov 1997 23:32:10 +1000
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=iso-2022-jp
- References: <199711060902.SAA02390@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
> Please forgive my ignorance, but someone could post a little > summary on what is the "i18n issue"? I usually leave such responses to others, but this time felt like chiming in :^) This is a much simpler concept than you think: Since words such as "internationalization" are long and hard to *say* much less to type, people who work in this field sometimes use abbreviations for them. The abbreviations are formed by removing all the characters in the word except the first and last, and replacing them with the number of characters that were removed, hence: internationalization = i18n multilingualization = m17n localization = l10n These are the main ones... if there are others, they've slipped my mind for now. Konna ni hima na yatsu mo iru'n da, tte omou deshou :^) H2e t2s h3s, Dave Next TLUG meeting is Saturday Dec. 13, 1997 (possibly Nov. 13?) --------------------------------------------------------------- a word from the sponsor: TWICS - Japan's First Public-Access Internet System www.twics.com info@example.com Tel:03-3351-5977 Fax:03-3353-6096
Home | Main Index | Thread Index
- Prev by Date: tlug: Simple Ghostview Question
- Next by Date: Re: tlug: Introduction; Looking for Help on i18n
- Prev by thread: tlug: Pine iso-2022-jp and Emacs
- Next by thread: tlug: Nov. 13 Evening Meeting
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links