documentation build updates #140
Conversation
* update readme to reflect build steps * add ccbya license to pom and repository to reflect footer used in docs * consistently build english and french as the default * seperate properties for translations to download, and languages to build * all profile is now only responsible for defining translations to download and langues to build Signed-off-by: Jody Garnett <[email protected]>
This appears to be accidentially committed some years ago Signed-off-by: Jody Garnett <[email protected]>
Signed-off-by: Jody Garnett <[email protected]>
Signed-off-by: Jody Garnett <[email protected]>
* Update readme to reflect build steps
* Add ccbya license to pom and repository to reflect footer used in docs
* Consistently build english and french as the default
* Seperate properties for translations to download, and languages to build
* All profile is now only responsible for defining translations to download and langues to build
* Disable colored output for build server
* Remove unused _build/locale folder
* Ignore Visual Studio Code and DS_Store files
Signed-off-by: Jody Garnett <[email protected]>
|
Manually merged in 07beec0 commit |
* Update readme to reflect build steps
* Add ccbya license to pom and repository to reflect footer used in docs
* Consistently build english and french as the default
* Seperate properties for translations to download, and languages to build
* All profile is now only responsible for defining translations to download and langues to build
* Disable colored output for build server
* Remove unused _build/locale folder
* Ignore Visual Studio Code and DS_Store files
Signed-off-by: Jody Garnett <[email protected]>
|
It looks like transifex is complaining
https://raw.githubusercontent.com/geonetwork/doc/develop/_build/locale/annexes/mef-format.pot Not sure how we could improve doc translation management but currently it looks like English pot files are used. |
|
How does this interaction work @fxprunayre? Was the |
Maybe something to ask to Maria ;) We only noticed that in last November doc sprint #82 and discussed a bit but with no easy workaround/solutions for this. From my point of view, translating line by line the doc in transifex does not look to be a good idea (but I'm not a transifex guru). Translating on github sounds much easier from a maintenance point of view even if it is maybe a bit more complex for translators? Would maybe need to be able to display 2 languages side by side ... So something to improve... |
One issue it that if you update the source file, then if we changed the english text, then transifex will cancel all existing translations - not tested but it is how it works for the json files... so I would be cautious updating that. At least it needs a test. |
|
Perhaps this change to remove |
Signed-off-by: Jody Garnett [email protected]