| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
QString::fromUtf16() is slow - it does a BOM check and optionally byte
swapping, which is utterly pointless when converting internal data
structures which are raw utf16 in host byte order anyway. so replace
it with QString::fromRawData() (for short-lived strings) or
QString(const QChar *, int) (otherwise) if possible.
Reviewed-by: axis
Reviewed-by: mariusSO
Reviewed-by: Bill King
|
|
|
|
| |
normalize the user input first
|
|
|
|
|
|
|
|
| |
if the pro file for the translations lives in a sibling tree of the
actual source tree, messages from included headers wouldn't have been
collected, as they were not considered part of the project.
Task-number: QTBUG-7495
|
|
|
|
| |
this has always been kind of an omission ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
previously, the semantics of nesting projects were pretty bizarre:
the list of TS files grew ever as the subdirs were visited. the
source files otoh were cleared for every project. this meant that
some TS files were updated over and over again, each time with different
data.
this is obviously total nonsense, so there is no compatibilty to keep.
so here come the new semantics:
- each project is scanned separately. it has separate include paths and
may override the inherited CODECFORSRC.
- the messages from all sub-projects are merged
- if a sub-project has a TRANSLATIONS entry, it is "detached" from its
parent project, thus starting an own merged translator. it is also
possible to name an empty set of TS files to simply exclude the
sub-project.
- CODECFORTR can be specified in each project with TRANSLATIONS
- if TS files are specified on the command line, they override
TRANSLATIONS from the top level project and stop processing of
detached projects alltogether. if multiple top-level projects are
specified, they are all merged.
this is somewhat slower, as now includes are re-scanned per project,
while previously all sources were simply accumulated and scanned as one
project. this can be fixed retroactively if needed.
|
|
|
|
|
| |
lrelease needs only the TRANSLATIONS value anyway, so there is hardly
anything to share for real
|
| |
|
| |
|
|
|
|
| |
really no point in doing so ...
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
tests/auto/linguist/lupdate/testlupdate.cpp
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
QIODevice: Fix readAll()
Temporary hackiesh solution to prevent BOM in the xml data.
Fixed qxmlstream autotest when using shadow builds.
Attempt at readding the capital P headers for Phonon
Remove special Phonon processing from syncqt.
Use the lowercase/shortname.h headers for Phonon includes
Fixes a crash when setting focus on a widget with a focus proxy.
Update copyright year to 2010
doc: Clarified activeSubControls and subControls.
Remove warning "statement with no effect"
doc: Clarified that .lnk files are System files on Windows.
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
of course, this will break if somebody actually pipes in windows files.
oh, well.
Suggested-by: joao
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-6072
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
92e9a48 ("eliminate Translator::replace()") eliminated the correctness
as well. whoops.
this code should be more efficient as well ...
|
| | |
| | |
| | |
| | | |
Reviewed-by: TrustMe
|
|/ / |
|
|/
|
|
| |
Task-number: QTBUG-6588
|
| |
|
|
|
|
|
|
| |
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 ...
|