* Fix rm ... output issue
Remove files only if they exist
* Fix Italian missing translations
There have been only 362 instead of 365
Sorry for that, normally I double check this.
* Added `not_tran` and `not_used` files
This makes it easier to find missing or obsolate translations
* Revert "Added `not_tran` and `not_used` files"
This reverts commit a1b53dde663dc20a105fd3fa817e612ef999cb97.
These should be ignored
* Ignore ALL `not_tran`and `not_used` files
* Add and update missing translations
- updated in Firmware/ files the missing `c=xx` column and `r=yy` rows.
- added missing translations to lang/lang_en*.txt
Everyone is developing and adding messages to serial and especially to LCD PLEASE add `//// c=xx` or `//// c=xx r=yy` comments.
Preparing translations files without that information is a pain in the ... and takes way more time for somebody else
to review to code as it would take you.
* No need to have `MSG_abcde` again in comments `////` in `messages.c`
* German translation
* Missed a space
* Use the same format as somewhere else
* French translation.
I am not a native French speaking person, so please excuse my mistakes I may have done.
* Spanish translation.
I am not a native Spanish speaking person, so please excuse my mistakes I may have done.
* CZ translation
* Fix typos
* Another fix
It is
Dimmwert and not Dim Wert
* Fix issues reported by `lang-check.py`
* Add "difficult" messages containing `%`
* Updated MSG and German translation
* removed a translation as it breaks the language selection
* No need to wait until any-key is pressed
* No need to wait any-key is pressed
* Fixed two LF issues
* Updated PO files
ready to be send to translators
* Add missing italian translations
* Improve some existing italian translations
* More italian fixes
* More italian fixes
* Add exceptions in editorconfig for po files to avoid recoding
* Fix typo
Thanks @DRracer for pointing out
* Italian translation by @wavexx
* Update po/new/*.po files
* Update after merging MK3 branch
* Update French translation and some c=xx comments
Big thanks to @awenelo @carlin57 for helping with the french translations and their comments.
* Update po files after French translation
* Fixed most `lang-check.py` reported translation errors for Czech and German.
Two Czech have to be reviewed as these are too long.
One German is correct as it is shown in c=20 r=2 but is 1 char longer than this to split the message.
One German translation seams to be to long but have to review the actual max length
* Fix `lang-check.py` Spanish translation errors
There have been quite lot TOO long messages,
Can't imagine that nobody every complained about that.
* Fix `lang-check.py` Italian translations errors
* Update not_tran and not_used files after fixing several translations
* Some more error fixes and update of `po` files
* Polish translation
* Czech updated
* Fix typo
* no need to translate `\x00` if it is the same
* Polish: Runouts->Koniec
* Polish: Runouts->Konce f ... hopefully the last change
* Added MK2.5/s auto power mode to eeprom doxygen
* Final updates.
- Compiled all versions with multi-languages
- Compiled all versions with EN_ONLY
- updated all /lang/po/Firmware*.* files
* Add crlf attributes for po files
As done for editorconfig, this similarly forces git to handle
po files consistently in DOS format.
* Further improvent of IT translations
* Updated translation
Added cleanup to PF-build.sh
* remove lang/not_tran* and lang/not_used mistakenly added into the PR
Co-authored-by: DRracer <drracer@seznam.cz>
Co-authored-by: Yuri D'Elia <wavexx@thregr.org>
Co-authored-by: D.R.racer <drracer@drracer.eu>
to have seperated build enviroments depening on Arduino IDE versions and board-versions.
Successfully tested with:
- Arduino IDE 1.8.5 and board version 1.0.1
- Arduino IDE 1.8.5 and board version 1.0.2
- These two above generate identical hex files
- Arduino IDE 1.8.7 and board version 1.0.2
- Arduino IDE 1.8.8 and board version 1.0.2
- Arduino IDE 1.8.9 and board version 1.0.2
- These three above generate identical hex files
- Compared to the 1.8.5 hex files the code uses less resources (Multi language/EN_ONLY):
```
Sketch uses 240082 bytes (94%) of program storage space. Maximum is 253952 bytes.
Global variables use 6002 bytes of dynamic memory.
Sketch uses 222344 bytes (87%) of program storage space. Maximum is 253952 bytes.
Global variables use 6019 bytes of dynamic memory.
```
vs.
```
Sketch uses 241526 bytes (95%) of program storage space. Maximum is 253952 bytes.
Global variables use 6046 bytes of dynamic memory.
Sketch uses 223828 bytes (88%) of program storage space. Maximum is 253952 bytes.
Global variables use 6065 bytes of dynamic memory.
```
Failed tests:
- Arduino IDE 1.8.6 and board version 1.0.2
- Arduino IDE 1.8.10 and board version 1.0.2
As I am planning to add new Prusa Arduino_Boards definition version 1.0.2 which contains few changes which interfere withthe existing PF-build.sh using Arduino_Boards v1.0.1,
i had to add an additional variable.
I have tested PF-build.sh with Arduino_Boards v1.0.1 and v1.0.2
It creates identical firmware hex files, if I manage it to run in the same minute.
If one of the runs is off by a minute compared to the other there is just one line in the hex code different,
which is showing the compiling date, time and firmware version.
- Changed Build-env path to "PF-build-dl" as requested in PR https://github.com/prusa3d/Prusa-Firmware/pull/2028
- Changed Hex-files folder to PF-build-hex as requested in PR
- Added Finding OS version routine so supporting new OS should get easier
What has changed:
- It downloads Arduino IDE 1.8.5 just once. Good for future build enviroment versions
- Uses Prusa Arduino_Boards. At this moment it download my 3d-gussner fork/branch/release. Pull request is made to DRracers his fork ... and finally to Prusa repository
- Minimized PF-build-env to changed files only. At this moment it only \hardware\tools\avr\avr\lib\ldscripts\avr6.xn
Old but updated:
Arduino IDE is portable and this build environment can be used with GUI.
Important preferences are set during istallation.
One thing users need to do is to go to Boardsmanager and search for Prusa and use EINSy board.
