Overview

Project website tigase.net
Instructions for translators

This is a project containing documentation for all Tigase XMPP Server components
Project maintainers User avatar qian User avatar andrzej User avatar wojtek
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/tigase/tigase-server.git
Repository branch master
Last remote commit Fixed eventbus serialization test #1521 7e92f3c8b
User avatar andrzej authored yesterday
Last commit in Weblate Add toString() to DataRepositoryImpl/Pool 1c8a88432
Wojciech Kapcia authored 8 months ago
Weblate repository http://translate.tigase.net/git/tigase-xmpp-server/dg-experimental/
File mask src/main/restructured/locale/*/LC_MESSAGES/Tigase_Development/Experimental.po
Translation file Download src/main/restructured/locale/pl/LC_MESSAGES/Tigase_Development/Experimental.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 76 2,192 13,146
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 76 100% 2,192 100% 13,146
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 78 changes 0 changes 6 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

2,192
Hosted words
76
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar qian

New strings to translate

Tigase XMPP Server / DG-Experimental — Polish

4 new strings to translate appeared to the translation. a year ago
User avatar qian

Resource update

Tigase XMPP Server / DG-Experimental — Polish

The "src/main/restructured/locale/pl/LC_MESSAGES/Tigase_Development/Experimental.po" file was changed. a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

If you want to pass configuration to your implementation simply use ``@ConfigField`` annotation on your variable (see :ref:`Component implementation - Lesson 2 - Configuration<cil2>` for more details).
 
a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

:ref:`Bosh Session Cache<boshsessioncache>`
 
a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

:ref:`Mobile Optimizations<mobileoptimizations>`
 
a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

:ref:`Dynamic Rosters<dynamicRosters>`
 
a year ago
User avatar None

New strings to translate

Tigase XMPP Server / DG-Experimental — Polish

76 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

Tigase XMPP Server / DG-Experimental — Polish

File src/main/restructured/locale/pl/LC_MESSAGES/Tigase_Development/Experimental.po was added. a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

**bosh-resource-bind** - The user resource bind is also cached to allow the client quickly retrieve information about the full JID for the established Bosh session.
 
a year ago
User avatar None

String updated in the repository

Tigase XMPP Server / DG-Experimental — Polish

**bosh-roster** - The user roster is cached in the Bosh component in exactly the same form as it was received from the core server. The Bosh Cache might or might not do optimizations on the roster like removing elements from the cached roster if the roster **remove** has been received or may just store all the roster requests and then send them all to the client. There is a one mandatory optimization the Bosh Cache must perform. It must remember the last (and only the last) presence status for each roster item. Upon roster retrieving from the cache the Bosh component must send the roster item first and then the presence for the item. If the presence is missing it means an offline presence. If the roster is small it can be sent to the client in a single packet but for a large roster it is recommended to split contact lists to batches of max 100 elements. The Bosh component may send all roster contacts first and then all presences or it can send a part of the roster, presences for sent items, next part of the roster, presences for next items and so on.
 
a year ago
Browse all translation changes