This PR adds the possibility to load the localizable strings from a specified localizable strings file. Also moved a localized string from the albumTitleView to the LocalizableStrings file.
Why
I was starting to host the localizable strings in a third party tool. From there the keys are exported again and reused in an Android project. There it is not possible to have keys with a dash in it. Tatsi has a few keys with this character in it. Renaming the keys is not a good solution as this breaks backward compatibility for everyone using the library. Best seemed to me to specify a localizable strings file using the tableName parameter of the NSLocalizedString initialiser.
This PR adds the possibility to load the localizable strings from a specified localizable strings file. Also moved a localized string from the albumTitleView to the LocalizableStrings file.
Why I was starting to host the localizable strings in a third party tool. From there the keys are exported again and reused in an Android project. There it is not possible to have keys with a dash in it. Tatsi has a few keys with this character in it. Renaming the keys is not a good solution as this breaks backward compatibility for everyone using the library. Best seemed to me to specify a localizable strings file using the
tableName
parameter of the NSLocalizedString initialiser.