Feedback after translating shared strings for Gecko 48:
- My main issue is that the comparison isn't styled like a diff program
which scrolls side by side (used a vertical split view) and doesn't
highlight added/removed blocks.
- At the moment, the todo list is the list of entities in the left
sidebar which is sorted alphabetically. Often some entities are related
and are only a few lines away from each other but the entities start
with different letters. Being aware that they are all up for translation
improves the quality.
- The autocomplete only looks up one word and not the whole text.
- The autocomplete suggestions are sometimes shown over the next line
which I need for context.
- The "+" for a new file which is new in the English 'locales' directory
adds it to the German repository, but doesn't run |hg add <file>
- The text highlight is not always obvious, e.g. after doubleclicking an
entity from the entity sidebar.
- Personally, I prefer to have the original (here: en-US) on the left
and the modification (here: de) on the right, but I might get used to it.
Bye
Sebastian
-------- Original-Nachricht --------
Betreff: Testing instructions for Aisle, and Testers wanted!
Von: Axel Hecht <[email protected]>
Datum: 2015-09-23 20:24
Hi,
I think that Aisle is in a state where it'd be good to get the first
suite of testers on it. Technical skillz required, though.
Known bugs: The panels don't always show up. Select a different panel,
and resize the window (in that order). Should help.
Set-up should be fairly low-impact on your machine, node 0.12 works fine.
First, you'll need to install the c9 SDK.
https://cloud9-sdk.readme.io/v0.1/docs/running-the-sdk is describing how
to do that.
Check that your local install works via
../server.js -p 8080 -a :
-p specifies the port, "-a :" says that you don't need auth.
Next up, install compare-locales. You'll want the one from version
control, https://github.com/Pike/compare-locales/. Either install that
globally, or in a virtualenv. Make sure you're running server.js in that
virtualenv. I haven't tested the virtualenv bit, but I expect it to work.
Next up, create a workspace. This is where your actual localization work
will happen. You'll want a clone of your l10n-central repo, and a clone
of mozilla-central. For those having all kinds of upstream repos, I'd
not point c9 to that, as searching for files will be yuck.
Let's assume you have the following structure in your workspace:
- l10n-central
- de (or it, fr, you'know)
- mozilla-central
Next up, bootstrap that workspace with c9, via
../server.js -p 8080 -a : -w /path/to/workspace
Open the url, and close the tab, and close the instance.
In /path/to/workspace/.c9 there should be a project.settings file.
That's a json file, add the following to the dict:
"moz_compare_locales": {
"json()": [
{
"l10n": "/l10n-central/",
"locales": [
"de"
],
"l10nini": [
"/mozilla-central/",
"browser/locales/l10n.ini"
]
}
]
}
Again, replace your locale code. Currently, aisle only supports the
first locale on that list. Also, make sure that the paths have a leading
and trailing '/'. (There's no UI for this yet)
Head over to another dir where you put random source stuff. Now we're
installing Aisle locally. Clone https://github.com/aisle-moz/moz.aisle,
cd into moz.aisle and run
c9 install .
(c9 is a global node package, the initial setup commands should install
that, IIRC)
Now head to http://localhost:8000/ide.html?debug=2. It should show a
"You are in Debug Mode" header in green. That's OK for you. I think.
Create a vertical split, menu flow is View -> Layout -> Vertical Split
Open up the "Compare" panel on the left, and see compare-locales output.
double click on a file will open the file in the upper side of your
vertical split.
Open up the "File" panel just beneath it, and see the comparison for
this file. It'll also open up the en-US file that corresponds to that.
Both panels have some weirdness in terms of actually showing their
content. If you don't see what you expect, open up a different panel
like "Commands", go back and give the window size a twist. I spent half
a day trying to figure out why, to no avail. I'll reach out upstream,
but for now, the workarounds only seem to be needed on first load.
Comments welcome to this group, or to
https://bugzilla.mozilla.org/enter_bug.cgi?product=Localization%20Infrastructure%20and%20Tools&component=Aisle.
Or bug me on irc, vidyo etc.
For general docs on how to use c9, https://docs.c9.io/docs/keybindings
is a good start. You'll want to cherry pick the docs that are about
editing.
Thanks for your help
Axel
_______________________________________________
tools-l10n mailing list
[email protected]
https://lists.mozilla.org/listinfo/tools-l10n
