Difference between revisions of "Subfolder under locale folder"
(→Subfolders under locale folder) |
(→Subfolders under locale folder) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
Example: |
Example: |
||
| + | '''en''' |
||
| − | <code> |
||
| + | content |
||
| − | ;en |
||
| + | ContentIntro.dita |
||
| − | : ''content'' |
||
| + | services |
||
| − | :: ContentIntro.dita |
||
| + | ServicesIntro.dita |
||
| − | :: ''services'' |
||
| + | '''fr''' |
||
| − | ::: ServicesIntro.dita |
||
| + | content |
||
| − | ;fr |
||
| + | ContentIntro.dita |
||
| − | : ''content'' |
||
| + | services |
||
| − | :: ContentIntro.dita |
||
| + | ServicesIntro.dita |
||
| − | :: ''services'' |
||
| − | ::: ServicesIntro.dita |
||
| − | </code> |
||
== 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 == |
||
Latest revision as of 18:59, 16 July 2020
Subfolders under locale folder
There are some resource files, such as DITA .dita and .ditamap or .adoc files, 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
The following is an example of settings for a DITA projects with .dita and .ditamap files to be translated from English (en) to French (fr).
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.
