bf6a2a2bf1
Previously, hrev55011 introduced localization for Cortex, which then prompted to close #7530. It has then been reopened, when it turns out that the translations for the container application (RouteApp) did not work, whereas the individual add-ons/modules were translated. The cause is that by default BCatalog looks up the translations based on the subtype part of the signature. This is x-vnd.Cortex.Route (without the application/ supertype). This change will place the translations in the right place of the file system. The add-ons were never affected, since they BCatalog is explicitly told to find the translations for the entire signature, like: static BCatalog sCatalog("application/x-vnd.Cortex.InfoView"); Even so, it was chosen to omit the `application` supertype from the signature for the shared code as well. This should fix #7530 for good. Change-Id: Iff18fabef7aba68602e49db1e98cfed2f486f545 Reviewed-on: https://review.haiku-os.org/c/haiku/+/4091 Reviewed-by: Niels Sascha Reedijk <niels.reedijk@gmail.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.