| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
this makes sense if one uses lupdate only for validation purposes, i.e.
to find out if the code uses only ids which are defined in some external
specification.
|
|
|
|
|
| |
when comparing two messages which both have ids, compare only the ids.
this affects finding/reporting duplicates and merging.
|
|
|
|
| |
preparation work ...
|
| |
|
|
|
|
|
|
|
|
|
| |
in a ts file, the top level categorization are the contexts, so it makes
no sense to make messages adjoint by file when the context is different.
a more clever algorithm which tries to order the entire contexts is
conceivable. that would be advantageous for files which use multiple
contexts subsequentially if each context appears in only one file.
|
|
|
|
| |
replace the one use case with something more efficient
|
| |
|
|
|
|
| |
consistent with all other source parsers
|
|
|
|
|
|
|
|
| |
two messages with identical singular but different plural sources simply
make no sense.
this should be quite a bit faster, as it saves lots of QHash<QString,...>
lookups.
|
|
|
|
| |
it was once needed for QMap, but we don't use that any more
|
|
|
|
| |
... with gotos :)
|
| |
|
|
|
|
| |
maemo *really* want it, so pushing it in now ...
|
|
|
|
|
| |
collect the files into a string list during the initial run instead of
iterating the argument list twice.
|
|
|
|
| |
to avoid the insane number of function arguments in a few places
|
| |
|
|
|
|
|
|
|
|
| |
this has two effects:
- using-declarations which use forward-declared classes work without
collecting the forward declarations, as the resolution happens at a
place where the class definition must have been encountered already
- it should be a bit faster
|
|
|
|
|
|
| |
the optimization not to look for parent definitions if we already knew
that there would be none did not consider that we only know that the
leaf node is missing, not any intermediate nodes.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Pierre Rossi
|
|/
|
|
| |
Reviewed-By: Oswald Buddenhagen
|
| |
|
|
|
|
|
|
| |
there must be a space after the //: and similar comments, otherwise
harmless comments of the sort of //====== foo here ===== will be parsed
as message ids, etc.
|
| |
|
|
|
|
| |
otherwise the fallback to use the source string is rather pointless
|
|
|
|
| |
unfinished messages
|
|
|
|
| |
--help says it does, but it didn't really.
|
|\ |
|
| |
| |
| |
| | |
-help says it does, and it kinda makes sense
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
with the current scheme of running "make ts" only when doing a
particular translation and checking in only the relevant file, these
files are never updated.
lconvert can generate an empty template from any translation anyway.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
xlf uses xx-YY notation instead of xx_YY
Reviewed-by: ossi
|
| |
| |
| |
| | |
"A class with a reference member must have a user-defined constructor."
|
|\ \
| |/
| |
| |
| | |
Conflicts:
translations/qt_ru.ts
|
| |
| |
| |
| |
| | |
Merge-request: 1611
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
qms are installed centrally from the top-level install target
|
| |
| |
| |
| |
| | |
this will save quite some hash lookups (even if in empty hashes)
and make the VisitRecorder bitmap smaller.
|
| |
| |
| |
| |
| | |
drop the parse results of files which are unlikely to be included (i.e.,
which are not headers).
|
| |
| |
| |
| |
| |
| | |
which means that one can set an arbitrary context.
as a side effect, this caches the stringified context of
Q_OBJECT-derived classes.
|
| |
| |
| |
| |
| |
| | |
... by virtue of the Q_DECLARE_TR_FUNCTIONS macro.
so remove the artificial limitation to classes (which was mostly an
optimization anyway).
|
| |
| |
| |
| |
| |
| |
| | |
do not import all data from included files into the current file (which
turned out to be extremely expensive for 3rdparty/webkit), but do
hierarchical lookups on demand. this makes the lookups as such much
slower, of course, but it still pays off.
|
| | |
|
| |
| |
| |
| |
| | |
they don't create useful namespaces and don't hold flags, so it is
pointless to clutter the namespace maps with them.
|
| |
| |
| |
| | |
no need for parameter "unresolved"
|
| |
| |
| |
| | |
needsTrFunctions was never set any more
|
| |
| |
| |
| |
| | |
cuts away a few thousand instructions.
need to revisit this in case of making the parser a dynamic library.
|