Feedback on "Creating en-X-dude", tooling comments?
Axel Hecht
I have just finished a wikicast on how to create a new language pack for
a dummy localization. The scope of that document isn't locked down,
though it shouldn't get much longer. More detailed information can
easily go to other pages.
As you can see, there are a few bugs mentioned still, I hope I caught
them all.
What I'd like to hear, would such a page be useful to newcomers? How big
are the differences to the process if you'd be using a more elaborate
tool than a plain text editor? Translate toolkit people, MT people, can
you try?
Oversimplification is OK, this is really a script for a screencast in my
head, they'll never tell you the naughty things.
Axel
Marek Stępień
> I have just finished a wikicast on how to create a new language pack for
> a dummy localization. The scope of that document isn't locked down,
To make things clear, Axel is talking about this document:
http://developer.mozilla.org/en/docs/Creating_en-X-dude
BTW, wouldn't wiki.m.o be a better place for such docs? It's rather an
internal doc, not something that should be placed on a more external MDC...
Axel Hecht
I consider it technical developer documentation. I don't think it's
internal nor process specific, but just runs developers through a bunch
of steps that many of them may go through at a point.
And did I dumb ass really forget the URL? Duh :-( Thanks for fixing that.
Axel
Ricardo Palomares Martinez
> What I'd like to hear, would such a page be useful to newcomers? How big
> are the differences to the process if you'd be using a more elaborate
> tool than a plain text editor? Translate toolkit people, MT people, can
> you try?
With MT you don't really need to do the dummy localization step; every
non-translated file will be exported as the en-US original file
(except, maybe, by the order of strings). However, the module mapping at:
http://developer.mozilla.org/en/docs/Creating_en-X-dude#DTDs
is not done 'automagically'; you have to tell MT that export directory
for "mozilla/browser/locales/en-US/" path will be
"l10n/[:locale:]/browser/" (actually, I set "mozilla" as the base
import directory and "l10n" as the base export directory, so I drop
both from the above expressions.)
Other than that, there is no difference. Anyway, I'll give it a shot.
What it could be done in the MT wiki page (or docs, but wiki seems
better to me) is to write a section named "Following 'Creating
en-X-dude' tutorial using MT'" to outline the differences, so the main
tutorial don't get polluted and people willing to use MT don't have to
find out themselves where the instructions diverge. Something similar
could be done for Translate Toolkit and other tools, I suppose.
Ricardo
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
