...So, I want to get involved into the Mozilla project.
So you're not involved already? You had me fooled. :)
Hehe; what I meant was contributing in a more direct (physical?) way. Actually improving the website/browser instead of tell people they filed the wrong bug or posting ideas on how to solve things. (Although I will keep doing that as well.)
Indeed. Most of the files should be updated to match the style guide. The style guide might need some updates as well with regard to character encoding et cetera.
Send suggestions either to n.p.m.documentation or directly to me.
> After that, new Bugzilla components might be needed for i18n of the website.
That's a good idea.
devmo? developer.mozilla.org perhaps?
yep. If you have a better short name, though, we're open to suggestions. :)
> I haven't seen that term yet, maybe one to add to the jargon file :-)
I was thinking, a database-driven glossary would be more useful than a jargon file.
http://bugzilla.mozilla.org/show_bug.cgi?id=202689
What do you think?
Optimizing the URI structure,
If you're want to tinker with that, *let me know*. I spent over a year chatting with mpt about it, and I'm slowly tweaking things in line with that plan.
That is quite some time. I heard, from mpt, that he stopped with the project.
You asked him about it?
> There are a lot of things that just seem wrong, a lot of files
are in the root directory were it would make more sense to put the in some "category directory" where they belong.
There hasn't really been anyone keeping tabs on the site organization these many years. It's like a big cauldron where everyone dumps things rather than like an organized filing system.
> That way the sub navigation bar would make a lot more sense too, I hope.
Yeah
...converting the files to UTF-8 so we don't need entities or character references for i18n.
Ah, ok. The style guide would need to be updated as well to say that files need to be encoded in UTF-8 rather than iso-8859-1. Now the whole site is mostly English, this isn't really a problem.
However, when we are doing more and more things with regard to i18n, like creating Japanese pages having UTF-8 is really nice, since it supports every Unicode character out there without the need for character references or entities (but that may be obvious).
Oh, I certainly agree. The only reason it's not in the Style Guide is that I didn't know how well it would work with our current system. Tell me when you think I should add it in, and if authors need to do anything special (e.g. add a <meta> tag). I'll then check with website-drivers and, if they're ok with it, add it to the Style Guide.
I can help out with HTML, XHTML, Atom, RSS, CSS, SQL, HTTP and other web related specifications.
Just for future reference, do you know Perl as well?
Not yet. I guess I could learn it, since I already know PHP, but I would have to buy some book or read some online tutorials. I did hear Perl is a bit outdated... Python seems to be very hot these days under the people who think PHP is actually just crap :-)
Ok
I have read your documents already. I really like them.
Yay. :)
> Now the only left to do is to make mozilla.org match those documents. A > lot of documents already validate, but their semantics aren't really good. > I think I'm going to file bugs for those to get some discussion going on,
on how to improve those. If solutions are found I'm willing to patch them.
If you get bogged down in review, don't leave the bug. Ask for what you've got so far to be checked in because it will be an improvement. We can always leave the bug open for further work.
~fantasai
-- http://fantasai.inkedblade.net/contact
_______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
