At yesterday (12.45 29 March 2008) I went to join the BugAThon event at Coffee world in Silom Rd. near Häagen-Dazs® ice cream, far from BTS Sala Deang 200 m and opposite CP tower building.

I arrived around 13.00. I didn’t found anyone with out the young member @dtinth, so I scared that I go to a wrong place. Then I tweet to @kengggg via twitter. He told me @pittaya and @kamthorn was on the road. While I was waiting for everyone, I was downloading the Firefox 3 Nightly Build to @kengggg. When both guys arrived for a while. @pphetra was coming and he went to talk about my work on JE virus inhibitor. I explained with confusing in mine mind. We waited @kengggg and @neung came and then @phisite was coming. @bact and ezy was coming before . @poakpong is the last one.

(The order has some wrong ordering. Please inform me)

When @bact came, we started to fix Firefox Bugs by distributed the Firefox Nightly Build and fixed the 1st Bugs. During the Bugs fixing, we had @ripmilla (Suphadech from แบ๋ ไต๋ ไฮเทค TV show) and people from opensourcemagazine came to looking our work.

We fixed the Thai Bugs for Thai Support and hope to make it to be Thai official support in Firefox 3. The Bugs is 65896 - Thai support — tracker bug

so this is the 1st to the last bugs

Bug 100173 – Thai language selection broken.

• BugAThon Thailand. we confirmed this works ok. This Bugs was close.

Bug 156881 (text-decoration-mode) – Underline should skip character/part-of-character that is below the base line (text-decoration-mode)

• BugAThon Thailand: We all agreed that this bug is not a blocking bug for Thai support. (i.e. just optional, good to have, but not necessary)

Bug 157534 – Edit->Find in Page found substring in Thai display cell, but it shouldn’t be

• BugAThon Thailand: We (7-8 native Thais) discussed about this and all agreed that while searching substring is expected behavior, searching substring starting with non-base Thai character is a non-expected behavior.

As a result, we should not allow user to type non-base Thai character at the start of string (e.g. search word, url) at the first place. i.e. we should do character sequence checking in find and address bar

If we can strict that input, anomalies in Bug 157534 and Bug 421275 will no longer appear. So both will be closed. New Bug 425900 open “Should not allow non-base Thai character as first character in textfield/textarea”.

Bug 157541 (CTL-render-textfield) – not enough foot room in textfield/location bar to display lower-level (part of) characters

• BugAThon Thailand: severity: normal -> minor

note: Official support language like “Gujarati” (Indo Arayan language) do has this problem too.

Bug 167983 – text with Thai/non-Thai combination, highlighting is not match with selection](https://bugzilla.mozilla.org/show_bug.cgi?id=167983)

• BugAThon Thailand: Mac OS X, Windows, Linux tested - works for me.

Bug 168762 (thai-unix.js) – RFE: unix.js needs font definitions for Thai locale

• BugAThon Thailand: We will close this bug as duplicate of Bug 284265 from Bug 284265, we settled with this:

Windows:

• serif: Tahoma
• sans-serif: Tahoma
• monospace: Tahoma

Linux:

• serif: serif
• sans-serif: sans-serif
• monospace: monospace

Mac OS X:

• serif: Thonburi
• sans-serif: Thonburi
• monospace: Ayuthaya

Bug 283283 – Invalid combining character sequences display incorrectly

• BugAThon Thailand: this is font-dependent and os-dependent, Firefox works consistent with native apps, we decided that this is not a bug, won’t fix.

Bug 226420 (thai-localization) – Thai Localizatoin/Translation — tracker

• BugAThon Thailand: We will translate document as fast as possible to make Firefox 3 will be Thai official.

Bug 284265 – Default Thai fonts should be set appropriately on each platform

• BugAThon Thailand: proposal for default font and default font sizes:

font.default.th = sans-serif

Windows:

• font.size.variable.th = 16
• font.size.fixed.th = 13
• font.minimum-size.th = 10

Linux:

• font.size.variable.th = 16
• font.size.fixed.th = 13
• font.minimum-size.th = 13

Mac OS X:

• font.size.variable.th = 16
• font.size.fixed.th = 13
• font.minimum-size.th = 10

Bug 353776 – need the surrounding text support for some language input

• BugAThon Thailand: on Firefox 3 Beta 5pre, Mac OS X and Windows also has this problem.

On Mac OS X, this behavior is consistent with native apps. On Linux, depends on IM system the user used.

On Linux, the user can notice this very explicitly, visually. On Mac OS X, the user can notice this as well, but the difference is very marginal, have to carefully spot it. On Windows, the user cannot notice this at all, visually.

Bug 421275 – Thai above and below vowels display incorrectly in URL bar

• BugAThon Thailand: We (7-8 native Thais) discussed about this and all agreed that while searching substring is expected behavior, searching substring starting with non-base Thai character is a non-expected behavior. As a result, we should not allow user to type non-base Thai character at the start of string (e.g. search word, url) at the first place. i.e. we should do character sequence checking in find and address bar. If we can strict that input, anomalies in Bug 157534 and Bug 421275 will no longer appear. So both will be closed.

New Bug 425900 open “Should not allow non-base Thai character as first character in textfield/textarea”

Bug 425900 – [CTL] Should not allow non-base Thai character as first character in textfield / textarea

• BugAThon Thailand: Found on Mac OS X and Linux ( Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008031317 Firefox/3.0b4 ). Works fine with Windows. Currently, in Firefox 3 Beta (Mac OS X and Linux), textfield/textarea allow input that starts with non-base Thai character (like upper/lower vowels, or some special symbols), this behavior will lead at least two anomalies:

Bug 421275 – Thai above and below vowels display incorrectly in URL bar

Bug 157534 – Edit->Find in Page found substring in Thai display cell, but it shouldn’t be

(more strange behavior of this Bug 157534 is that, since Firefox/Gecko will not highlight single lone non-base character — user will see that Find bar report that it found a search string, but he will not see any highlighted text as expected).

We propose that textfield/textarea should not allow user to enter any non-base Thai character at the start of string. i.e. do sequence checking.

Bug 425915 – word boundary detection for Thai text

• BugAThon Thailand

  • Word boundary detection is needed for various text-related functions in Firefox, including:
  • navigation/selection/editing by keyboard: caret moving by word (current the caret wasn’t move into word)
  • selection by mouse: double-clicking on text should select word (not the whole text between whitespaces)

Conclusion: We closed 7 Bugs, 5 Bugs was remain and 2 Bugs was open.

After the work we have the Ubuntuclub came to see us and they give us a ubuntuclub pin. After for awhile kla and hunt came to talk to us. When 20.00 is the earth hour. That is a time to save energy. Then this is a time to go home.

Tag in : BugAThon

Update: I changed the BugATHon Bangkok into BugAthon Thailand name because @bact had noticed me, we had a member was watching us through Bugzilla. This is the link form @bact for promote the Bugs 226420 (thai-localization) – Thai Localizatoin/Translation — tracker talking BugAThon Thailand, seeing Firefox Thai Official Localization plan, This Bugs we need the team to translate it into Thai language.