Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Use for search:
    • Normal search: Match the string given in the Search field
    • Wildcards: The string can contain the wildcard characters 
      • ? (single character) 
      • * (any group of characters)
    • Regular expression: The search string is interpreted as a MySQL regular expression, except some regular expressions, that are black-listed for technical reasons.
      • Please see the MySQL regular expression documentation for details on how to use regular expressions
      • The following table illustrates some commonly used metacharacters and constructs in a regular expression, that are allowed to use in translate5:

        MetacharacterBehavior
        ^matches the position at the beginning of the searched string
        $matches the position at the end of the searched string
        […]matches any character specified inside the square brackets
        [^…]matches any character not specified inside the square brackets
        *matches the preceding character zero or more times
        +matches preceding character one or more times
        {n}matches n number of instances of the preceding character
        {m,n}matches from m to n number of instances of the preceding character

         

      • The following list contains the regular expressions and regular expressions search string validation patterns , which are not supported by translate5, because they are black-listed:

         
        Hexadecimal escape | \xFF where FF are 2 hexadecimal digits | Matches the character at the specified position in the code page | \xA9 matches © when using the Latin-1 code page
        RefexDescription
        \x[a-fA-F0-9]{2}RegexDescription
        \nCharacter escape
        \rCharacter escape
        \tCharacter escape
        \fCharacter escape
        \vCharacter escapec[a-zA-Z]Control character escape \cA through \cZ Match an ASCII character Control+A through Control+Z, equivalent to \x01 through \x1A \cM\cJ matches a Windows CRLF line break. Control character escape \ca through \cz Match an ASCII character Control+A through Control+Z, equivalent to \x01 through \x1A \cm\cj matches a Windows CRLF line break
        \0NULL escape
        \(?:[1-7][0-7]{0,2}|[0-7]{2,3})1 or \2 etc.Octal escape (Any character with a character code lower than 256 ex: \251)
        (.*)\|(.*)javascript: a|ab matches a in ab | In POSIX ERE: a|ab matches ab in ab
        \\[\^\]\-]Some Characters | Some CharactersUsing | for and "or" regex
        \^ or \] or \- or \\\ (backslash) followed by any of ^-]\
        \bjavascript: [\b\t] matches a backspace or a tab character.
        \Bjavascript: \B. matches b, c, e, and f in abc def
        \dShorthand Character Classes
        \DShorthand Character Classes
        \sShorthand Character Classes
        \SShorthand Character Classes
        \wShorthand Character Classes
        \WShorthand Character Classes
        \hShorthand Character Classes
        \?\?e. g. a regular expression like abc?? matches ab or abc
        \*\?".*?" matches "def" and "ghi" in abc "def" "ghi" jkl
        \+\?".+?" matches "def" and "ghi" in abc "def" "ghi" jkl
        {[0-9],[0-9]}\?{1,1}? Matches exactly one time (meaningless quantifier)
        {[0-9],}\?Matches between one and unlimited times, as few times as possible, expanding as needed 
        \u[a-fA-F0-9]{4}Specific Unicode code points can not be searched with regular expressions. The code point shown here is an example. ex: \u78af
        \(\?\:.*?\)Non-capturing parentheses group the regex so you can apply regex operators, but do not capture anything.
        \(.*?\)=\\[0-9](abc|def)=\1 matches abc=abc or def=def, but not abc=def or def=abc.
        \(\?\=.*?\)Matches at a position where the pattern inside the lookahead can be matched. Matches only the position. It does not consume any characters or expand the match. In a pattern like one(?=two)three, both two and three have to match at the position where the match of one ends.
        \(\?\!.*?\)Similar to positive lookahead, except that negative lookahead only succeeds if the regex inside the lookahead fails to match.
        \[\:(.*)\:\]This regex will validate if the user enters '[:(.*):]'

        The following table illustrates some commonly used metacharacters and constructs in a regular expression.

        MetacharacterBehavior^matches the position at the beginning of the searched string$matches the position at the end of the searched string[…]matches any character specified inside the square brackets[^…]matches any character not specified inside the square brackets*matches the preceding character zero or more times+matches preceding character one or more times{n}matches n number of instances of the preceding character{m,n}matches from m to n number of instances of the preceding character
        is not supported.
        *?
        +?
        OTHERSOther regular expressions, that are similar to the listed expressions are also not supported. The front-end of translate5 will tell you, if a regex is not supported. Please contact translate5 lead development at MittagQI, if you have more questions about this.


  • Save segment on close: If checked (by default yes), the segment will be saved when is closed via search navigation

  • Search on locked segments: If checked, segments that are locked for editing are searched, too.