Include and Exclude Patterns: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
Rdaly (talk | contribs)
No edit summary
Rdaly (talk | contribs)
No edit summary
Line 5: Line 5:


For example:
For example:
# If all the resource files are in a folder called <code>resources</code> then the  '''Include Pattern''' would be <code>**/resources/**</code>
# If all the resource files are in a folder called <code>resources</code> then the  '''Include Patterns''' would be <code>**/resources/**</code>
# If there is a file such as <code>config.properties</code> which is not a resource file, then the '''Exclude Pattern''' would look like <code>**/config.properties</code>
# If there is a file such as <code>config.properties</code> which is not a resource file, then the '''Exclude Patterns''' would look like <code>**/config.properties</code>


Select '''Next'''
Select '''Next'''

Revision as of 16:59, 1 September 2023

This is used to denote resource locations or to verify that other files are not mistaken for resource files.

For example:

  1. If all the resource files are in a folder called resources then the Include Patterns would be **/resources/**
  2. If there is a file such as config.properties which is not a resource file, then the Exclude Patterns would look like **/config.properties

Select Next

Step 9: Optional Advanced Localyzer Settings



Step 1:Data Source Credential for the project

Step 2:Choose a Repository

Step 3: Name the Project

Creating a Globalyzer Project - Step 4: Globayzer Lite Definition File

Creating a Localyzer Project - Step 5: Which MT or TMS will Localyzer use

Step 6: What are the locales Localyzer is acting on?

Step 7: Resource file formats

Step 8: Set up optional include or exclude patterns

Step 9: Optional Advanced Localyzer Settings

Step 10: Grant Users and Teams Access