-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathHOWTO
More file actions
30 lines (17 loc) · 2.65 KB
/
HOWTO
File metadata and controls
30 lines (17 loc) · 2.65 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Fender Software Localization Guide
Copyright (c)2026 Fender Musical Instruments Corp. All Rights Reserved.
INTRODUCTION
Fender software products like Studio Pro (and its predecessor PreSonus Studio One) can be localized for for multiple languages via language packs. A language pack is basically a ZIP archive containing all resources for a certain language such as strings used in menus and in the application windows and dialogs.
String tables are based on the GNU gettext file formats. For more information on GNU gettext please refer to https://www.gnu.org/software/gettext/. Additionally, there are some text resources which need to be translated separately.
GETTING STARTED
The file and folder structure for a new language will be setup in the translations repository by Fender. Start by examining the string folders for your language. For Fender Studio Pro (and PreSonus Studio One) you can find them here:
"translations/modules/strings/<language-code>"
"framework/translations/modules/strings/<language-code>"
"foundation/translations/modules/strings/<language-code>"
These folders contain all .po files for the given language that make up the main part of the translation effort.
Please note that for versions 6.0 to 6.5 they are located in "translations/modules/<module>/strings/<language-code>" and for versions prior to version 6, they are located in "translations/strings/<language-code>".
For Studio Pro, there are currently about 7000 strings which need to be translated. Additionally, it is required to translate the device descriptions found in "foundation/translations/resources/devices/<language-code>" and the EULA in "foundation/build/identities/fender/eula".
LOCALIZATION TOOLS
You can use any software localization tool compatible with the .po file format. However, if you do not have a preferred translation workflow yet, we recommend using the latest version of the CCL Localizer application available at https://ccl.dev/tools. Besides translation editing, it also enables you to build language packs on your local system for testing purposes. The CCL Localizer project file for Studio Pro can be found in the path translations/projects/studioapp/studioapp.lzproject. Opening this file requires the whole directory tree to be copied/cloned to your local system. Please update to the latest version of CCL Localizer before starting the translation as it might contain new features that are necessary to load the project file.
DEPLOYMENT
Language packs for our products are hosted on Fender Exchange (https://my.fender.com/exchange/). The final step of preparing the installation file for your language pack extension will be done by Fender.