Subfolder under locale folder: Difference between revisions
| Line 16: | Line 16: | ||
== Setting up a project where the resource files are located in subfolders under a locale folder == | == Setting up a project where the resource files are located in subfolders under a locale folder == | ||
See [[On_Boarding_an_LRM_Project|''Onboarding an LRM project'']] for information on how to set up a LRM project. | See [[On_Boarding_an_LRM_Project|''Onboarding an LRM project'']] for information on how to set up a LRM project. Below is an example of how to setup a resource extension where the files are located in subfolders under a locale folder. | ||
In the file structure example above, there are base resource files located in the ''./en/content'' folder as well as the ''./en/content/services'' folder. In the Jenkins Project configuration, you'll need to define 2 resource extensions where the extension name and parser type are the same, but the folder name patterns are different. The folder name patterns must have a wildcard (*) after the locale pattern (l_c_v) and must have the ''Use Location Pattern on Default Locale'' checked. | |||
[[File:DitaResourceExtensions.png]] | [[File:DitaResourceExtensions.png]] | ||
Revision as of 23:01, 8 July 2020
Subfolders under locale folder
There are some resource files, such as DITA, that require a file structure where there are subfolders under each locale folder.
Example:
- en
- content
- ContentIntro.dita
- services
- ServicesIntro.dita
- fr
- content
- ContentIntro.dita
- services
- ServicesIntro.dita
Setting up a project where the resource files are located in subfolders under a locale folder
See Onboarding an LRM project for information on how to set up a LRM project. Below is an example of how to setup a resource extension where the files are located in subfolders under a locale folder.
In the file structure example above, there are base resource files located in the ./en/content folder as well as the ./en/content/services folder. In the Jenkins Project configuration, you'll need to define 2 resource extensions where the extension name and parser type are the same, but the folder name patterns are different. The folder name patterns must have a wildcard (*) after the locale pattern (l_c_v) and must have the Use Location Pattern on Default Locale checked.
