| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an element, such as <p>, has a name="translatable" attribute, we
also want to grab markup tags inside the element and translate them as
well.
For example, previously this HTML:
<p name="translatable">An embedded <b>tag</b> in a paragraph</p>
would result in the following string being extracted:
_("An embedded");
However, we want it to be:
_("An embedded <b>tag</b> in a paragraph");
This removes the use of BeautifulSoup from the eos-html-extractor script.
Unfortunately BeautifulSoup could have done this quite easily, but it
does not provide any line number information, which we need. Previously
in order to get the line numbers we also used html.parser from Python's
standard library, to augment the data we got from BeautifulSoup. However,
this issue required html.parser to do all the work that BeautifulSoup did
anyway, so there is no reason to use BeautifulSoup anymore.
[endlessm/eos-sdk#3291]
|
| |
|
|
|
|
|
| |
When generating the .dummy.c file, eos-html-extractor previously did not
escape quotes correctly.
[endlessm/eos-sdk#3291]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Whitespace between words and tags doesn't matter to HTML. Indeed, the
text in a translatable element may be formatted any way over any number
of lines, so we normalize all consecutive whitespace to be just one space
character and strip whitespace from the beginning and end of the strings.
This is so that translators are not confronted with strange newlines and
whitespace on Transifex.
[endlessm/eos-sdk#3291]
|
| |
|
|
|
|
|
|
|
| |
This gets the underlying byte stream of sys.stdout and wraps it in a
UTF-8 encoder. That is then used as the default output file rather than
sys.stdout itself, which on Jenkins may not have a default encoding of
UTF-8.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
|
|
| |
Since this is Python 3, we can specify at file-open time what the
encoding of the input and output files is to be. This should fix any
build errors with non-ASCII characters in an ASCII terminal environment.
[endlessm/eos-sdk#3245]
|
| |
|
|
| |
Try to fix a Jenkins test failure.
|
| |
|
|
|
|
|
|
| |
I noticed that --version gave the wrong description, so I removed the
description entirely. I changed the help string to parallel that of
eos-html-extractor.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
| |
May as well be forward compatible, while we're touching this.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
|
| |
eos-html-extractor would crash if it encountered some text comment before
it had encountered a comment.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
| |
Another minor cleanup; TranslatableHTMLParser shouldn't use global state.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
|
| |
We don't need to import all of os, just os.path; and urllib was not
necessary for reading the file.
[endlessm/eos-sdk#3245]
|
| |
|
|
| |
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
| |
For more consistency in command line argument handling.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is taken almost directly from the existing version in eos-english.
Cleanups to follow in subsequent commits. Previously the m4 code was in
two separate macros, but since they were much the same, I combined them
into one macro.
This also adds a very minimal test for eos-html-extractor; basically as
a very quick regression test for the cleanups to follow.
[endlessm/eos-sdk#3245]
|
| |
|
|
|
|
|
| |
This test runner dates from even before eos-jasmine, and is not used
anywhere.
[endlessm/eos-sdk#3054]
|
| |\
| |
| | |
First round of dev vm preparation scripts
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| |
| |
| | |
per task
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | | |
|
| |/
|
|
| |
[endlessm/eos-sdk#475]
|
| |\
| |
| | |
#335 Integrated JSON extraction utility
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The utility used in eos-english and eos-programming-app was integrated and installed as part of the SDK
CR comments addressed include:
- Integrated new facilities available on GTK
- Removed duplicate prototype declaration
- Reformatted CLEANFILES var declaration
- Used configure.ac to get @PACKAGE_VERSION@
- Added version() and usage() utilities
[endlessm/eos-sdk#335]
|
| |\ \
| |/
|/| |
Use System.exit() and System.programInvocationName
|
| | |
| |
| |
| |
| |
| |
| | |
In GJS >= 1.38, these facilities are available. This removes the
workarounds that we had for lack of these facilities.
[endlessm/eos-sdk#432]
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This implements the 'init' subcommand of the application manifest tool,
which creates a new manifest in the current directory.
[endlessm/eos-sdk#154]
[endlessm/eos-sdk#154]
|
| | |
| |
| |
| | |
[endlessm/eos-sdk#154]
|
| |/
|
|
|
|
|
| |
$libexecdir/eos-application-manifest, instead of
$datadir/eos-application-manifest
[endlessm/eos-sdk#154]
|
| |
|
|
|
|
|
|
| |
This is the framework for an 'eos-application-manifest' tool with
subcommands as in git. Currently the 'help' and 'version' subcommands
are implemented.
[endlessm/eos-sdk#152]
|
|
|
This adds a script eos-run-test which is adapted from gjs_run_tests,
but does not try to discover the tests itself. Instead, in keeping with
Automake's test suite facilities, it takes the filename of a test to run.
[endlessm/eos-sdk#290]
|
