Meeting1 - Mon 28 April, 2008 (5pm)
Venue
Room 605, 6th floor, NSTDA Building, Rama6 Road.
Participants:
- Thaweesak Koanantakool (Hugh), NECTEC
- Kamthorn Krairaksa, NECTEC
- Krit Kowasat (Bomb), NECTEC
- Samphan Raruenrom, Open Source Development
- ศุภฤกษ์ วินา, Open Source Development
- Poakpong Phongsasanongkul, Khun Kajorn's representative (e-printing, Adobe)
- Trin Tantsetthi (Conductor), Internet Thailand (WTT 2.0)
- Theppitak Karoonboonyanan (Thep), Free software developer (libthai, GNOME)
- Pattara Kiatisevi (Ott), MM Technology (KDE, Qt)
- Jakkapun Kwanroengjai (กอล์ฟ), MM Technology (KDE, Qt)
- Vuthichai Ampornaramveth, MM Technology (SimpleThai, cttex)
- Arthit Suriyawongkul (Art/bact'), SIIT, Thammasat University
- Patipat Susumpow (Keng), OpenDream
- Patcharaporn Pansuwan (Neung), OpenDream
- Martin Hosken, Payap University
- Sira Nokyoongtong (Mara/มะระ), UbuntuClub
- Phisit Siprasatthong
- James Clark, Thai Open Source Software Center
- Fukiat Julnual, Microsoft Thailand
- (not presented) Virach Sornlertlamvanich (Tid), Thai Computational Linguistics Lab
- (not presented) Dome Charoenyost
Add your name/surname/nickname here.
Facilities to be prepared
- Video projector [ok]
- White board [ok]
- WiFi access guest coupons [ok]
- Simple dinner [ok]
Objectives of this meeting
- To kick off the WTT3 task force, and define the scope and priority of what to do
- To outline the overall plan for WTT3
- To assign lead author/editor of each topic in the draft
- To agree upon the top three deliverables which we can complete within the next three months
- To approve the frequency of meeting and other management issues, including funding, if required.
Proposed Agenda
- Agreement on the proposed agenda [add your comment below]
- What do we want to have in WTT3 (Please read and put your vote on this Worksheet)
- What other works do we want to write about, as a supplement to WTT3.
- Delegation: who will lead each "topic" of WTT3.
- What should be the first three deliverables, and the delivery date?
- Date of the next meeting. Expected frequency of real meeting.
- Discussion on the use of Wikidot: is it good enough, or we change to something better?
Minutes of Meeting
- WTT guidelines [Hugh]
- Persists in the long future
- Adaptable to dynamic changes of technologies
- Minority language coverage?
- Mobile input? (an example: Chinese Pinyin)
- Incident table still 2D?
- International concerns [James]
- WTT should specify standards in international context, not just national
- Script vs. language should be distinguished
- WTT 2.0 situations [Trin]
- Multi-level I/O strictness
- Systems with full conformances: Solaris, OO.o, XIM, SCIM
- Only covers Thai language, Pali & Sanskrit transliteration using Thai alphabets
- [James] Specifications for Latin script already cover many languages, why not for Thai script?
- Minority languages concerns
- [Martin] As many as 50 languages are being written with Thai script
- [Martin] Some more examples: กี็๋ กื็๋ แ็ า็
- Principle: Different strings must be rendered differently
- [bact] Should input and output be separated?
- [bact] How about same string which is allowed in minority languages but not allowed in Thai language, e.g. ก็่? Should it be rendered differently in different languages?
- [Martin] How about the case of กูํ or กํู ? What is the accepted order?
- [Trin] According to WTT concept, กูํ is the canonical order, กํู is not
- Unicode allows both, with normalization requirement in all algorithms
- [Trin] Unicode is repeating our failure in the past, before WTT 2.0 addressed it
- [Trin] Extra level for minority languages?
- [James] Technical support level, such as OpenType variation selection, is another detail to determine
- [Trin] Canonical string is the real core of WTT concept, not input/output
- [Vuthichai] Agreed. Input sequence correction should be allowed, as long as canonical string is resulted
- Typographical issues [Poakpong]
- Should common typographical practices, like spacing, be described as guidelines or recommendations?
- Common keyboard shortcuts for special characters?
- The use of ZWSP
- Proper font support
- Some problems [Poakpong]
- UTF-8/UTF-16 confusion on Mac
- [Trin] UTF-8 and UTF-16 are clear standards, should not be issue
- [Kamthorn] PUA problem?
- [Trin] MacThai is proprietary standard, not official, and should not be used for transmission
- [Thep,Vuthichai] Probably a bug of Firefox Mac version?
- UTF-8/UTF-16 confusion on Mac
- Options [Trin]
- Drop WTT 2.0?
- Extend the scope of WTT 2.0 for more languages written with Thai script?
- Develop a shared library?
- WTT 3.0 Categories [James]
- Encoding
- Display (+ line wrapping)
- Editing (input sequence, caret movements, backspace, delete, etc.)
- Sorting
- Working Groups [Hugh]
- DEE = Display + Encoding + Editing
- S = Sorting
- Other issues
- [Samphan] Thai alphabetical numbering
- [Trin] Law or parliament institutes should already have some standards
- String collation
- Two existing practices, from the same source (the Royal Institute Dictionary):
- Dictionary based: direct rule application
- Telephone directory based: with word boundary concern
- [Thep] Two implementation approaches with the same result:
- Unicode: re-ordering as preprocessing
- GNU C library: using collating elements to cope with re-ordering
- [James] Different results for invalid strings
- Two existing practices, from the same source (the Royal Institute Dictionary):
- [Samphan] Thai alphabetical numbering
- Collaboration tools [Trin]
- What to use? Is existing tools appropriate?
- Summary:
- wikidot as scratch board
- new wtt3 mailing list for discussion, in English, for easy reference in international documents moc.spuorgelgoog|3ttw#moc.spuorgelgoog|3ttw
- Volunteer:
- James as the draft editor
- Thep to prepare materials on string collation
- Participation
- [Poakpong] More linguists?
- [bact] Printing associations?
- IBM? (IBM National Language Development)
Minute taker: Thep
Other minutes:
- (Unofficial) บันทึกการประชุม WTT 3.0 ครั้งที่ 1 - Sira Nokyoongtong
Add a new comment
page_revision: 21, last_edited: 1209561143|%e %b %Y, %H:%M %Z (%O ago)





