| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
| |
Reviewed-by: Oswald Buddenhagen
modified: tools/linguist/linguist/messageeditor.h
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
after all, it is no good idea to announce the removal of all columns
just to let the view headers adjust themselves - it also makes the views
emit currentItemChanged() which has some undesirable side effects. so
don't do it an fix the header manually.
|
| |
| |
| |
| | |
Task-number: QTBUG-4429
|
| |
| |
| |
| |
| | |
otherwise qlocale will silently clobber the user's (most probably bogus)
choice anyway.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
there is really no point in doing so
Reviewed-by: hjk
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the translator comment field is not written out, so reading the
definition into it is basically discarding it as far as any roundtrips
which arrive at qph again are concerned.
the message's disambiguation seems most suitable for the task.
Reviewed-by: hjk
Task-number: QTBUG-4498
|
| |
| |
| |
| |
| |
| | |
qlocale.h includes qobjectdefs.h which forward-declares it as a class.
Reviewed-by: aportale
|
|/
|
|
| |
Reviewed-by: Thierry
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
The qlibraryinfo.cpp is only needed by lrelease. It has a hack for
qmake_libraryInfoFile(), which doesn't work on AIX. So don't put
qlibraryinfo.cpp in libbootstrap.a, but instead build directly for
lrelease.
Reviewed-by: thiago
|
|
|
|
|
|
|
|
|
| |
... so the tools are usable with QT_FATAL_WARNINGS.
it may be sensible to "degrade" the c++ parser warnings to info
messages. possibly later ...
Task-number: QTBUG-5683
|
|
|
|
|
|
| |
"This cannot happen" ... yeah, right. :}
Task-number: QTBUG-5989
|
|
|
|
|
| |
Task-number: QTBUG-4499
Task-number: QTBUG-5276
|
| |
|
|
|
|
| |
querying the actual codec before the file has been read is pointless
|
|\ |
|
| |
| |
| |
| | |
Over src/ tools/ examples/ and demos/
|
| |
| |
| |
| |
| |
| |
| | |
Also took care of placing non breakable spaces before double
punctuation characters.
Reviewed-by: Benjamin Poulain
|
| |
| |
| |
| | |
qsettings_win needs advapi32
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
needed for build-time qm generation in qt itself.
the downsides are a) that the other bootstrapped tools grow by ~12kB
(on x86) due to qdatastream being pulled in by qbytearray and qstring
and b) that lrelease isn't l10n'd itself anymore (the latter could be
fixed by building a non-qobject qtranslator).
|
|/
|
|
| |
preparation work for bootstrapping
|
|
|
|
|
|
| |
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
|