| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I9e6e15cc5a5597586b4a913e0cc75cf337ddfc05
|
|
Change-Id: I3df1216054c133314b2317849744a0a37e9fbc8f
Reviewed-on: https://gerrit.libreoffice.org/13733
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I3fe9bea58c9b4005336bafcf3b779d18c89df971
|
|
With earlier version of fgc, one could cd into a sub directory and
use fgc to find the German comments in there.
This change restores that behaviour again.
Change-Id: I2fa30ff98af0418c7531b94f19ff0b81f76abddd
Reviewed-on: https://gerrit.libreoffice.org/11522
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I1d7c1fa2fffe20a0bc60cf5533b8f8c28e360a1d
|
|
Change-Id: I3d452ac218005b40568ec116ede9962cc1e60a18
|
|
I ran pylint and corrected the following errors:
* W: 39,0: Unnecessary semicolon
* W:177,0: Bad indentation. Found 19 spaces, expected 20
* W:178,0: Bad indentation. Found 19 spaces, expected 20
* W:213,0: Unnecessary semicolon
* W: 65,8:Parser.get_comments: Unused variable 'linenum'
* C:190,28:Parser.check_file: Operator not preceded by a space
* C:192,24:Parser.check_file: Operator not followed by a space
* C:196,24:Parser.check_file: Comma not followed by a space
* W:223,33:Parser.check_source_files: Redefining built-in 'dir'
Change-Id: Idd4986fecb7b3a2af87d1062b7d08c6c87b9f80f
Reviewed-on: https://gerrit.libreoffice.org/10475
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
In calculating how many tabs to use for the display,
when the path was more than 40 characters (like for
dbaccess/source/ui/relationdesign/RelationTableView.cxx)
it returned '1, 0' for the number of tabs --
and python didn't like that. Return 1 instead.
Change-Id: If370ffe03b4aff67ca59094dd38863986ca39519
Reviewed-on: https://gerrit.libreoffice.org/9239
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Instead of recreating a text_cat sub-process for every string, start a
single text-cat process (with the -s flag, "per line") and reuse that.
Testing on svl/source shows a speed-up of 7.5 x, down from 45.6s to 6.1s!
To avoid blocking on the pipes set autoflush in text-cat, and use
read_line instead of read on the find-german-comments side.
Change-Id: Ic6c00fc3c1e7cbcbbfff65512bf54ad11f900697
Reviewed-on: https://gerrit.libreoffice.org/9226
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Change-Id: I48b5c6afe861704abe978cb07ecd9df6e39d7b7c
|
|
Change-Id: I12b9d5816c685b2374e6d659436e46965f29cd3a
|
|
Change-Id: I2a0a14c905ec1ba1408b625894ba0b8a02e17aa7
|
|
Change-Id: Ic8d5861fda5b21df43447eb7bc4dc9a416ce1afb
|
|
Change-Id: Ice848243654b1bc8923ba65fe87c61e8087c0d8a
|
|
The new option "-L" allows to print out potential candidates for translation
combined with the number of lines found like "-l" - but only if there was a
positive result (i.e., a file that needs checking).
This leads to a much more compact representation helping people to find the
few files that still need translations.
Change-Id: Iad554eb6ce5b062e96774d9488c54105679b7c4b
|
|
|
|
This adds the argument -f (--filenames-only), which only prints the
filenames of files containing German comments.
I personally scan the whole file for German strings anyway, as we do
not find German strings with less than 4 chars. So there's not so
much use in printing the found strings.
|
|
|
