https://github.com/mulle-cc/mulle-genstrings
🗻 Create Localizable.strings from NSLocalizedString
https://github.com/mulle-cc/mulle-genstrings
foundation localization mulle-objc objective-c
Last synced: about 1 year ago
JSON representation
🗻 Create Localizable.strings from NSLocalizedString
- Host: GitHub
- URL: https://github.com/mulle-cc/mulle-genstrings
- Owner: mulle-cc
- License: bsd-3-clause
- Created: 2022-12-18T18:59:15.000Z (over 3 years ago)
- Default Branch: release
- Last Pushed: 2024-12-18T17:06:45.000Z (over 1 year ago)
- Last Synced: 2025-01-30T13:12:59.924Z (over 1 year ago)
- Topics: foundation, localization, mulle-objc, objective-c
- Language: CMake
- Homepage:
- Size: 111 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# mulle-genstrings
#### 🗻 Create Localizable.strings from NSLocalizedString
> An old project, that may or may not work, but which will be resurrected
> eventually.
This is like a version of Apple's genstrings first dumbed down
and then put on steroids. With it's added muscle it is able to merge changes
with the Localizable.strings file.
The dumbing down, means that it only has limited options. It always reads
UTF8 files and it always writes UTF16 files. Dumbest of all, it can only deal
with one keyword NSLocalizedString (or a substitution keyword)
mulle-genstrings tries not to "fix" genstrings
behaviour too much, except when the output would be clearly broken.
In my tests, the files created by mulle-genstrings are identical
to the files created with genstrings.
## Usage
Assuming your project is in english and you wrote:
NSLocalizedString( @"foo", @"this is foo as a verb");
You want to run `mulle-genstrings -o en.lproj *.m` to generate the english
Localizable.strings and `mulle-genstrings -a -m de.lproj -o de.lproj *.m`
for other language projects. This will ensure, that old translations will not be
overwritten and new keys are added.
You can additionally also specify `.strings` files as input sources. These will not
be scanned for `NSLocalizedString` but parsed as `.strings` files. This makes it
easy to merge files.
### -a option: append only
Only useful in conjunction with the -m option, this will not overwrite previous values for keys.
### -f option: force output
If mulle-genstrings doesn't find any localizable strings, no output will be
generated. You can force the generation of an output file with "-f".
### -m option: specify merge source
**mulle-genstrings** can merge strings files. Here you specify a source, that you
want to merge with. Additionally specify "-a" if you want to keep the original
values intact.
### -s option: change search key
You can change the term to search for instead of `NSLocalizedString`. Useful if
you follow the suggestions from [Localizing library code, the right way ?](//www.mulle-kybernetik.com/weblog/2015/localizing_library_code_the_r.html).
### -t option: translate value
You can push each localizable strings value through a translate script. The script is specifed with the -t option. Every occurence of {} will be replaced with the value to translate.
The script should echo the translated value.
As an example the "ms-translate.sh" script is provided, that uses [Microsofts Translation API](https://msdn.microsoft.com/en-us/library/mt146806.aspx)
to translate pages. You would call **mulle-genstrings** with `-t "./mulle-ms-translate.sh de pt {}"` to create a translated `Localizable.strings` from german to portugese.
In order for this script to work, you have to register with Microsoft and get the proper secret into `~/.mulle-genstrings-v0/secret`. Currently the MS translation API is free for small loads.
## Author
Coded by Nat! on 16.10.2014