Before I make the extension public...

There are a few things that I should do before I make the Tagalog language pack public.

• Take some time off
  
  I've been looking over the translations so long that they make sense. What I mean to say is that I need some time away from them so that I can take a look at them will a fresh set of eyes. Of course, I'll have a link for people to make comments or report bugs, but the last thing that I want to address is an influx of the same issues again and again. So, that brings me to the next thing.



• A web page
  
  A page where I can put the language pack and show others how to install the language pack or how they should contact me if they would like to see a change.



• Another look over the text
  
  Although the translations are pretty much what I've decided to use, the next issue, aside from the terms themselves is SYNTAX. Let's face it, if you don't know what a term is, you can discern its meaning simply from it's context... or at least infer its meaning. That requires good syntax. Tagalog and other Filipino languages have a PREDICATE-TOPIC structure, or, rather VERB-SUBJECT-OBJECT word order. That poses some issues and so, some sentences that follow this with apposition (NOT opposition), the sentence becomes lop-sided. Tagalog has ways to "break" away from this rigid order, so some of the long sentences will have to be re-edited. Then, after release I can come back later and make further changes.



• Prepare for version 1.5.x
  
  The Mozilla Foundation has version 1.5 beta 2 out. I've looked at how the text is layed out and it's different from 1.0.7! No matter. It will just be a matter of moving text around. The issue will just be the amount of text which is ALL of it.
  



• Update tools
  
  I've metioned that Mozilla Translator (the link is broken unfortunately) is "usable" but there is a lot of "massaging" and manual things that need to be done to produce an XPI. If you don't know what you're doing (like I was before I found out that it's broken), it can be very frustrating. So, I created my own tool.
  
  
  That's the issue with my tool, however. I know that it's not perfect, but I know about it's pitfalls. If I gave it to someone else to use, then I'd have to support it, of course. At this time though, I'm revamping it's design and it's overall functionality because I've added features to it as I was localizing Firefox and trying it out with the Mozilla Suite. In essence, I hacked my own tool and I haven't tested it enough to know if it's usable for others. In addition, I'd like to write a help file to ship with it to lessen the impact of supporting it.
  



• Enlist help from others
  
  So, far the help that I'm getting is from posting on the various groups that I am a member of, such as Alibata, Wika and GMail-Phils. But, it would probably be easier if the work were to be split up into subsections, divide the labor. Then I would only have to act as management and editing.