mirror of
https://github.com/mod-playerbots/azerothcore-wotlk.git
synced 2026-01-13 17:19:07 +00:00
da884fea3e
Process of translation: only original sources of deDE texts by researching multiple sources, reverse translation by searching for related quest items/NPCs and using these names to reconstruct a proper translation. This fixes the terms Scrimshank (Kieselschliff), Banehollow (Schattenfluch), Trollbane (Trollbann), Stonesplitter (Splitterstein), Stonemaul (Steinbrecher), Captain (Hauptmann), Kromcrush (Krombruch), Earthbinder (Erdbinder), Razorfen (Klingenhauer), Razorflank (Klingenflanke), Stonard (Steinard) for quest progress/request text entries for the deDE localisation with proper casus/declension (these are not proper translated names of locations/NPCs that have been left over by Blizzard since their language localisations in TBC in 2006 and onward). Fixed a self-made translation for quest 334. Added missing deDE text entries for 4481, 4482, 4483, 5306, 5863, 7723, 9436. <!-- First of all, THANK YOU for your contribution. --> ## Changes Proposed: - Fixing missing or wrong entries in the quest_request_items_locale table. ## Issues Addressed: <!-- If your fix has a relating issue, link it below --> Fixes some of the tasks listed in the issues below: - https://github.com/azerothcore/azerothcore-wotlk/issues/14244 - https://github.com/azerothcore/azerothcore-wotlk/issues/14618 - From CC Github: https://github.com/chromiecraft/chromiecraft/issues/4697 ## SOURCE: <!-- If you can, include a source that can strengthen your claim --> Read the text on top. ## Tests Performed: <!-- Does it build without errors? Did you test in-game? What did you test? On which OS did you test? Describe any other tests performed --> - Not tested. ## How to Test the Changes: <!-- Describe in a detailed step-by-step order how to test the changes --> All of the changes are to request texts of quests, can be tested by accepting quests or simply reviewing the changed file. ## Known Issues and TODO List: <!-- Is there anything else left to do after this PR? --> - [ ] I still might want to check which of the tasks in above mentioned issues are resolved by this. <!-- If you intend to contribute repeatedly to our project, it is a good idea to join our discord channel. We set ranks for our contributors and give them access to special resources or knowledge: https://discord.com/invite/DasJqPba) Do not remove the instructions below about testing, they will help users to test your PR --> ## How to Test AzerothCore PRs When a PR is ready to be tested, it will be marked as **[WAITING TO BE TESTED]**. You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here: http://www.azerothcore.org/wiki/How-to-test-a-PR **REMEMBER**: when testing a PR that changes something **generic** (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but **especially** check that the PR does not cause any regression (i.e. introducing new bugs). **For example**: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but **we should test Y and Z as well**. Co-authored-by: Gultask <100873791+Gultask@users.noreply.github.com>