| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
the PO format doc suggests that all references are in
filename:linennumber format, but some tools seem to deviate from that.
so do our best to preserve such references, even if we can't do anything
with them.
Task-number: QTBUG-9488
|
| |
|
|
|
|
|
| |
after all, it is pretty much specific to xlf files, even if the problem
majorly concerns converted po files.
|
|
|
|
| |
ConversionData::error() does already newline-terminate the strings.
|
|
|
|
| |
Task-number: QTBUG-8044
|
|
|
|
|
|
|
|
| |
encoding the qt context as a magic comment was no particularly good
idea, as it provided no disambiguation as far as gettext is concerned.
so instead encode the context into msgctxt.
Task-number: QTBUG-10307
|
|
|
|
|
|
|
| |
Ossi is right: on WinCE, _setmode is different from regular Windows
and the docs...
Reviewed-by: ossi
|
|
|
|
|
|
| |
... both from windows and the wince doc ...
Reviewed-by: joerg
|
| |
|
|
|
|
| |
Reviewed-by: joerg
|
|
|
|
|
|
|
| |
At least with g++ 3.4 on Solaris, they are. So you can't write
::isalpha because that expands to something invalid.
Reviewed-by: Trust Me
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
... as this is what gettext processors expect.
|
|
|
|
|
| |
these are in fact the same as PO files, only that exporting to one
automatically drops translations.
|
| |
|
|
|
|
|
|
| |
instead of doing string editing magic, parse the header properly.
don't add a template file comment, either - it's not mandatory, after
all.
|
| |
|
|
|
|
|
|
|
| |
we set it to that value when writing xliff, as the header is mandatory
and no better value is possible. it seems unlikely that an unqualified
"english" would be used if somebody meant to actually specify a source
language, so this hack should be ok.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
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
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|/
|
|
|
|
|
| |
of course, this will break if somebody actually pipes in windows files.
oh, well.
Suggested-by: joao
|
| |
|
| |
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Task-number: QTBUG-4499
Task-number: QTBUG-5276
|
| |
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|