path: root/test/tools
Commit message (Collapse)AuthorAge
* Handle HTML with embedded tagsPhilip Chimento2015-06-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]
* Handle quotes in HTML stringsPhilip Chimento2015-06-18
| | | | | | | When generating the .dummy.c file, eos-html-extractor previously did not escape quotes correctly. [endlessm/eos-sdk#3291]
* Handle excess whitespace in stringsPhilip Chimento2015-06-18
| | | | | | | | | | | | 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]
* Add eos-html-extractor and m4 filePhilip Chimento2015-06-04
| | | | | | | | | | | | 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]
* Port eos-application-manifest tests to JasminePhilip Chimento2015-04-17
| | | | | | This somehow escaped Sam's big switcheroo last year. [endlessm/eos-sdk#3054]
* Remove ancient test runnerPhilip Chimento2015-04-17
| | | | | | | This test runner dates from even before eos-jasmine, and is not used anywhere. [endlessm/eos-sdk#3054]
* eos-application-manifest: Fix import path in testPhilip Chimento2013-12-09
| | | | | | All unit test files must import things relative to $(top_srcdir). [endlessm/eos-sdk#154]
* Subcommand 'eos-application-manifest init'Philip Chimento2013-12-09
| | | | | | | | | 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]
* First attempt at an EOS test runnerPhilip Chimento2013-09-16
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]