Difference between revisions of "Subfolder under locale folder"
(→Setting up a project where the resource files have subfolders) |
(→Setting up a project where the resource files have subfolders) |
||
| Line 15: | Line 15: | ||
::: ServicesIntro.dita |
::: ServicesIntro.dita |
||
| − | == Setting up a project where the resource files |
+ | == 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 example above, there are base resource files located in the ''./en/services'' folder as well as the ''./en/services/contents'' 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]] |
||
Revision as of 22:58, 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 example above, there are base resource files located in the ./en/services folder as well as the ./en/services/contents 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.
