- Posts: 796
Updating and internationalizing documentation
04 Apr 2017 20:47 - 04 Apr 2017 20:54 #61187
by Moeder
Replied by Moeder on topic Updating and internationalizing documentation
Oh yeah, it did in my test repo 
That's why I decided we just use the (not so) new cron feature from Travis. You can choose to trigger a build from any branch daily, weekly or monthly; the setup script will then check for $TRAVIS_EVENT_TYPE and only then push new translations to Github. We could also choose to only do the other builds when they are Github triggered, so the cron job is just used for updating the translations, which will in turn trigger a release build of the manual which will include the new translations.
That's why I decided we just use the (not so) new cron feature from Travis. You can choose to trigger a build from any branch daily, weekly or monthly; the setup script will then check for $TRAVIS_EVENT_TYPE and only then push new translations to Github. We could also choose to only do the other builds when they are Github triggered, so the cron job is just used for updating the translations, which will in turn trigger a release build of the manual which will include the new translations.
Please Log in or Create an account to join the conversation.
17 Apr 2017 20:48 #61531
by FDR
Replied by FDR on topic Updating and internationalizing documentation
@Moeder
First, congratulations for the completed german translation!
Second, we still have problems with uploading the documentations:
- The devo8 PDSs don't upload for a while because of this after_success condition:
- The old PDF versions are not deleted from the Downloads section. I do delete them manually. I will take care of this...
- Despite I haven't done the HTML upload, we will need a different after_success upload section for them.
- Don't you think we should rather have a special target for the cron job to refresh the translations, instead bounding that to the devo10 PDF build?
First, congratulations for the completed german translation!
Second, we still have problems with uploading the documentations:
- The devo8 PDSs don't upload for a while because of this after_success condition:
after_success:
- if [[ "$TRAVIS_EVENT_TYPE" == "push" && "$MAKETARGET" == "latexpdf-release" && "$TARGET" == "devo10" ]]; then
make gettext; sphinx-intl -c source/conf.py-intl update -p build/locale; tx push -s;
export TARGET_VERSION=$(echo $TARGET | egrep -o '[[:digit:]]{1,2}');
export TARGET_PDF=$(echo "devo${TARGET_VERSION}manual*.pdf");
echo "Uploading Documentation - $TARGET_PDF";
utils/upload_documentation.pl -documentation -pdf build/pdf-$TARGET/$TARGET_PDF;
fi;- The old PDF versions are not deleted from the Downloads section. I do delete them manually. I will take care of this...
- Despite I haven't done the HTML upload, we will need a different after_success upload section for them.
- Don't you think we should rather have a special target for the cron job to refresh the translations, instead bounding that to the devo10 PDF build?
Please Log in or Create an account to join the conversation.
17 Apr 2017 21:21 #61533
by Moeder
Replied by Moeder on topic Updating and internationalizing documentation
Happy Easter everybody!
After fixing the ifs (I just did another update on the PR) im back at 99 %...
I have to admit the model and protocol chapters were reeeeeally long and it was more of duty than joy to finish them
I inserted the devo10 condition because I thought it didn't make too much sense to do many 'make gettext' but it took a while for me to notice this killed the devo8 builds...
I will commit a change for a better .travis.yml
After fixing the ifs (I just did another update on the PR) im back at 99 %...
I have to admit the model and protocol chapters were reeeeeally long and it was more of duty than joy to finish them
I inserted the devo10 condition because I thought it didn't make too much sense to do many 'make gettext' but it took a while for me to notice this killed the devo8 builds...
I will commit a change for a better .travis.yml
Please Log in or Create an account to join the conversation.
25 Apr 2017 07:48 #61755
by Morlacus
Replied by Morlacus on topic Updating and internationalizing documentation
Going on....
I have found some words which would need to be translated in french in the lang.fr file :
Trainer Sw ; Num Channels ; Momentary : Toggle ; Extend ; offset ; nbr mixer : Mixer ; Delay ;
How to propose a translation. Is there a max length for the translation ?
Where to ask explanations about the original manual ? Is there a sort of bug report for this ? or a specific topic ?
Example : I dont understand the sentence concerning scale in the complex mixer :
Note that while the scale value is limited to 100%, the mixer may provide a value larger than 100% if an offset is set or if the trim value is non-zero
In fact the scale can be fixed from -125 to +125 so what is the limit ?
I have found some words which would need to be translated in french in the lang.fr file :
Trainer Sw ; Num Channels ; Momentary : Toggle ; Extend ; offset ; nbr mixer : Mixer ; Delay ;
How to propose a translation. Is there a max length for the translation ?
Where to ask explanations about the original manual ? Is there a sort of bug report for this ? or a specific topic ?
Example : I dont understand the sentence concerning scale in the complex mixer :
Note that while the scale value is limited to 100%, the mixer may provide a value larger than 100% if an offset is set or if the trim value is non-zero
In fact the scale can be fixed from -125 to +125 so what is the limit ?
Please Log in or Create an account to join the conversation.
Time to create page: 0.069 seconds
-
Home
-
Forum
-
Development
-
Development
- Updating and internationalizing documentation