mirror of
https://github.com/SoftFever/OrcaSlicer.git
synced 2025-08-09 14:55:08 -06:00
Change Application name to OrcaSlicer
This commit is contained in:
SoftFever
parent
81ca7720e9
commit
5b0ba1207e
93 changed files with 5629 additions and 10221 deletions
|
|
@ -1,4 +1,4 @@
|
|||
|
||||
# Building Bambu Studio on UNIX/Linux
|
||||
# Building Orca Slicer on UNIX/Linux
|
||||
|
||||
Currently Linux version is not verified, you can try it referring to [PrusaSlicer'S linux building guide](https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Linux%20et%20al.md)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
# Building Bambu Studio on Mac OS
|
||||
# Building Orca Slicer on Mac OS
|
||||
|
||||
## Enviroment setup
|
||||
Install Following tools:
|
||||
|
|
@ -11,7 +11,7 @@ Install Following tools:
|
|||
Cmake, git, gettext can be installed from brew(brew install cmake git gettext)
|
||||
|
||||
## building the deps
|
||||
You need to build the dependence of BambuStudio first. (Only needs for the first time)
|
||||
You need to build the dependence of OrcaSlicer first. (Only needs for the first time)
|
||||
|
||||
Suppose you download the codes into /Users/_username_/work/projects/BambuStudio
|
||||
create a directory to store the dependence built: /Users/_username_/work/projects/OrcaSlicer_dep
|
||||
|
|
@ -26,7 +26,7 @@ for x86 architeccture
|
|||
`cmake ../ -DDESTDIR="/Users/username/work/projects/OrcaSlicer_dep" -DOPENSSL_ARCH="darwin64-x86_64-cc"`
|
||||
`make -jN` (N can be a number between 1 and the max cpu number)
|
||||
|
||||
## building the Bambu Studio
|
||||
## building the Orca Slicer
|
||||
create a directory to store the installed files at /Users/username/work/projects/BambuStudio/install_dir
|
||||
`cd BambuStudio`
|
||||
`mkdir install_dir`
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# Building Bambu Studio on Windows
|
||||
# Building Orca Slicer on Windows
|
||||
|
||||
## Enviroment setup
|
||||
Install Following tools:
|
||||
- Visual Studio Community 2019 from [visualstudio.microsoft.com/vs/](https://visualstudio.microsoft.com/vs/) (Older versions are not supported as Bambu Studio requires support for C++17, and newer versions should also be ok);
|
||||
- Visual Studio Community 2019 from [visualstudio.microsoft.com/vs/](https://visualstudio.microsoft.com/vs/) (Older versions are not supported as Orca Slicer requires support for C++17, and newer versions should also be ok);
|
||||
- Cmake from [cmake.org](https://cmake.org/download/)
|
||||
- Git from [gitforwindows.org](https://gitforwindows.org/)
|
||||
- Perl from [strawberryperl](https://strawberryperl.com/)
|
||||
|
|
@ -18,7 +18,7 @@ create a directory to store the dependence built: D:/work/Projects/OrcaSlicer_de
|
|||
|
||||
It takes "00:14:27.37" to finish it on my machine (11th Gen Intel(R) Core(TM) i9-11900 @2.50GHz 2.50 GHz, with 32.0 GB DDR)
|
||||
|
||||
## building the Bambu Studio
|
||||
## building the Orca Slicer
|
||||
create a directory to store the installed files at D:/work/Projects/BambuStudio/install_dir
|
||||
`cd BambuStudio`
|
||||
`mkdir install_dir`
|
||||
|
|
@ -31,6 +31,6 @@ then build it using command
|
|||
`cmake --build . --target install --config Release`
|
||||
|
||||
or building it under the Visual Studio 2019
|
||||
(set the BambuStudio_app_gui as start project)
|
||||
(set the OrcaSlicer_app_gui as start project)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Localization and translation guide
|
||||
|
||||
The purpose of this guide is to describe how to contribute to the Bambu Studio translations. We use GNUgettext for extracting string resources from the project and PoEdit for editing translations.
|
||||
The purpose of this guide is to describe how to contribute to the Orca Slicer translations. We use GNUgettext for extracting string resources from the project and PoEdit for editing translations.
|
||||
|
||||
Those can be downloaded here:
|
||||
- https://sourceforge.net/directory/os:windows/?q=gnu+gettext GNUgettext package contains a set of tools to extract strings from the source code and to create the translation Catalog.
|
||||
|
|
@ -32,15 +32,15 @@ Notice. When the translation is complete you need to:
|
|||
- copy BambuStudio_xx.mo into resources/i18n/xx and rename it to BambuStudio.mo, then push the changed file.
|
||||
( name of folder "fr" means "French" - the translation language).
|
||||
|
||||
### Scenario 3. How do I add a new text resource when implementing a feature to Bambu Studio
|
||||
Each string resource in Bambu Studio available for translation needs to be explicitly marked using L() macro like this:
|
||||
### Scenario 3. How do I add a new text resource when implementing a feature to Orca Slicer
|
||||
Each string resource in Orca Slicer available for translation needs to be explicitly marked using L() macro like this:
|
||||
```C++
|
||||
auto msg = L("This message to be localized")
|
||||
```
|
||||
To get translated text use one of needed macro/function (`_(s)` or `_CHB(s)` ).
|
||||
If you add new file resource, add it to the list of files containing macro `L()`
|
||||
|
||||
### Scenario 4. How do I use GNUgettext to localize my own application taking Bambu Studio as an example
|
||||
### Scenario 4. How do I use GNUgettext to localize my own application taking Orca Slicer as an example
|
||||
|
||||
1. For convenience create a list of files with this macro `L(s)`. We have
|
||||
https://github.com/bambulab/BambuStudio/blob/master/bbl/i18n/list.txt.
|
||||
|
|
@ -75,14 +75,14 @@ https://github.com/bambulab/BambuStudio/blob/master/bbl/i18n/list.txt.
|
|||
When you have Catalog to translation open POT or PO file in PoEdit and start translating.
|
||||
|
||||
|
||||
## General guidelines for Bambu Studio translators
|
||||
## General guidelines for Orca Slicer translators
|
||||
|
||||
|
||||
- We recommend using *PoEdit* application for translation (as described above). It will help you eliminate most punctuation errors and will show you strings with "random" translations (if the fuzzy parameter was used).
|
||||
|
||||
- To check how the translated text looks on the UI elements, test it :) If you use *PoEdit*, all you need to do is save the file. At this point, a MO file will be created. Rename it Bambu Studio.mo, and you can run Bambu Studio (see above).
|
||||
- To check how the translated text looks on the UI elements, test it :) If you use *PoEdit*, all you need to do is save the file. At this point, a MO file will be created. Rename it Orca Slicer.mo, and you can run Orca Slicer (see above).
|
||||
|
||||
- If you see an encoding error (garbage characters instead of Unicode) somewhere in Bambu Studio, report it. It is likely not a problem of your translation, but a bug in the software.
|
||||
- If you see an encoding error (garbage characters instead of Unicode) somewhere in Orca Slicer, report it. It is likely not a problem of your translation, but a bug in the software.
|
||||
|
||||
- See on which UI elements the translated phrase will be used. Especially if it's a button, it is very important to decide on the translation and not write alternative translations in parentheses, as this will significantly increase the width of the button, which is sometimes highly undesirable:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue