Wyszukiwanie¶

Searching for strings¶

Advanced queries using boolean operations, parentheses, or field specific lookup can be used to find the strings you want.

When no field is defined, the lookup happens on source, target, and context strings.

Proste wyszukiwanie¶

Any phrase typed into the search box is split into words. Strings containing all of them are shown. To look for an exact phrase, put „the searchphrase” into quotes (both single (') and double (") quotes will work): "this is a quoted string" or 'another quoted string'.

Pola¶

source:TEXT

Wyszukiwanie bez rozróżniania wielkości liter w ciągu źródłowym.

target:TEXT

Target string case-insensitive search.

context:TEXT

Context string case-insensitive search.

key:TEXT

Key string case-insensitive search.

note:TEXT

Wyszukiwanie bez rozróżniania wielkości liter w opisie ciągu źródłowego.

location:TEXT

Location string case-insensitive search.

priority:NUMBER

Priorytet ciągu.

id:NUMBER

Unikalny identyfikator ciągu tekstowego.

position:NUMBER

Pozycja ciągu tekstowego w pliku tłumaczenia.

added:DATETIME

Timestamp for when the string was added to Weblate.

state:TEXT

Search for string states (approved, translated, needs-editing, empty, read-only).

This field also supports Operatory pól, so searching for completed strings can be performed as state:>=translated, searching for strings needing translation as state:<translated.

source_state:TEXT

Search for source string states, see above for more info.

pending:BOOLEAN

String pending for flushing to VCS.

has:TEXT

Search for string having attributes - plural, context, suggestion, comment, check, dismissed-check, translation, variant, screenshot, flags, explanation, glossary, note, label.

is:TEXT

Filters string on a condition:

read-only or readonly: Read-only strings, same as state:read-only.
approved: Approved strings, same as state:approved.
needs-editing or fuzzy: Needing editing strings, same as state:needs-editing.
translated: Translated strings, same as state:>translated.
untranslated: Untranslated strings, same as state:<translated.
pending: Pending strings not yet committed to the file (see Leniwe zatwierdzenia).

language:TEXT

Docelowy język ciągu.

component:TEXT

Component slug or name case-insensitive search, see Końcówka adresu URL komponentu and Nazwa komponentu.

project:TEXT

Project slug, see Końcówka adresu URL.

path:TEXT

Path to the object to limit searching inside component, category, project, or translation.

changed_by:TEXT

String was changed by author with given username.

changed:DATETIME

String content was changed on date, supports Operatory pól.

change_time:DATETIME

String was changed on date, supports Operatory pól, unlike changed this includes event which don’t change content and you can apply custom action filtering using change_action.

change_action:TEXT

Filters on change action, useful together with change_time. Accepts English name of the change action, either quoted and with spaces or lowercase and spaces replaced by a hyphen. See Wyszukiwanie zmian for examples.

source_changed:DATETIME

Source string was changed on date, supports Operatory pól.

check:TEXT

String has failing check, see Kontrole i korekty for check identifiers.

dismissed_check:TEXT

String has dismissed check, see Kontrole i korekty for check identifiers.

comment:TEXT

Szukaj w komentarzach użytkowników.

resolved_comment:TEXT

Szukaj w rozwiązanych komentarzach.

comment_author:TEXT

Filtruj według autora komentarza.

suggestion:TEXT

Szukaj w sugestiach.

suggestion_author:TEXT

Filtruj według autora sugestii.

explanation:TEXT

Szukaj w objaśnieniach.

label:TEXT

Szukaj w etykietach.

screenshot:TEXT

Szukaj w zrzutach ekranu.

Operatory logiczne¶

You can combine lookups using AND, OR, NOT and parentheses to form complex queries.

The NOT operator has higher precedence than the AND operator; the AND operator has higher precedence than the OR operator. You can add parenthesis to define a precedence of your own.

Omitting the operator will make the query behave like the AND operator was used.

Equivalent expressions¶
`(state:translated AND source:hello) OR source:bar`	Parenthesized expression to clearly show the precedence.
`state:translated AND source:hello OR source:bar`	The `AND` operator has higher precedence than the `OR` operator.
`state:translated source:hello OR source:bar`	Query using an implicit `AND` operator.

Operatory pól¶

You can specify operators, ranges or partial lookups for date or numeric searches:

state:>=translated: State is translated or better (approved).
changed:2019: Zmieniono w roku 2019.
changed:[2019-03-01 to 2019-04-01]: Changed between two given dates.
position:[10 to 100]: Strings with position between 10 and 100 (inclusive).

Dokładne operatory¶

You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly matching hello world, use: source:="hello world". For searching single word expressions, you can skip quotes. For example, to search for all source strings matching hello, you can use: source:=hello.

Wyszukiwanie zmian¶

Dodane w wersji 4.4.

Searching for history events can be done using change_action and change_time operators.

For example, searching for strings marked for edit in 2018 can be entered as change_time:2018 AND change_action:marked-for-edit or change_time:2018 AND change_action:"Marked for edit".

Wyrażenie regularne¶

Anywhere text is accepted you can also specify a regular expression as r"regexp".

For example, to search for all source strings which contain any digit between 2 and 5, use source:r"[2-5]".

Podpowiedź

The regular expressions are evaluated by the database backend and might use different extensions, please consult the database documentation below for more details.

PostgreSQL Regular Expressions Details (this is the default database engine for Weblate)
MariaDB Regular Expressions Overview
MySQL Regular Expressions

Wstępnie zdefiniowane zapytania¶

You can select out of predefined queries on the search page, this allows you to quickly access the most frequent searches:

Ordering the results¶

There are many options to order the strings according to your needs:

Searching for users¶

Dodane w wersji 4.18.

The user browsing has similar search abilities:

username:TEXT

Search in usernames.

full_name:TEXT

Search in full names.

language:TEXT

User configured translation language (see Tłumaczone języki).

joined:DATETIME

String content was changed on date, supports Operatory pól.

translates:TEXT

User has contributed to a given language.

You might want to limit contribution time by change_time, for example change_time:>"90 days ago".

contributes:TEXT

User has contributed to a given project or component.

You might want to limit contribution time by change_time, for example change_time:>"90 days ago".

change_time:DATETIME

Same as in Searching for strings.

change_action:TEXT

Same as in Searching for strings.

Additional lookups are available in the Interfejs zarządzania:

is:bot: Search for bots (used for project scoped tokens).
is:active: Wyszukaj aktywnych użytkowników.
email:TEXT: Search by e-mail.

Fuzzy values for DATETIME fields¶

Instead of using DATETIME values like MM-DD-YYYY, a string containing adverb of time like yesterday, last month, and 2 days ago can be used as values in the DATETIME fields.

Przykłady:

changed:>="2 weeks ago": Returns strings that are changed 2 weeks ago from the current date and time.
changed:>=yesterday: Returns strings that are changed starting yesterday.