Fix part of #5607: Prevent toolbar title truncation in AudioLanguageFragment at 200% font scaling

[anmoltrvd01]

Explanation

Fix part of #5607 (PR 11: Settings & Help)

This PR addresses a UI issue in AudioLanguageFragment where the toolbar title was truncated when the system font size was increased to 200% (Android 14+, non-linear font scaling).

Changes made:

• Introduced a custom TextView inside the Toolbar layout.
• Enabled marquee scrolling for the toolbar title to ensure the full text remains accessible..
• Configured the title to be focusable and selected programmatically to trigger marquee behavior.
• Ensured compatibility with large font sizes and display scaling settings.

Testing performed:

• Enabled 200% font scaling on an Android 14 emulator.
• Tested with maximum Display Size setting.
• Verified that the full toolbar title is visible without truncation.
• Tested in both portrait and landscape modes to ensure there is no overlap, clipping, or layout breakage.

Screenshots (before/after) are attached below:

Before

After

PreferredAudioLang.mp4

(Enabled 200% font scaling & Tested with maximum Display Size setting.)

[anmoltrvd01]

Hi @adhiamboperes,
It looks like the workflows are awaiting maintainer approval since I’m a first-time contributor.
Could you please help approve and re-run them when you get a chance?
Thank you!

[adhiamboperes]

Hi @anmoltrvd01, We typically don't make the toolbar text wrap, but we have an option called marquee, you can see an example of thei in TopicActivity and ExplorationActivity, please take a look at those and let me know if you have any questions.

[adhiamboperes]

Thanks @anmoltrvd01! please make the changes I have suggested, and I will run your CI checks. I know that because the current changes are only xml related, the checks would pass.

[oppiabot]

Hi @anmoltrvd01, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[anmoltrvd01]

Hi @adhiamboperes,
Thank you for your earlier feedback. I’ve addressed the requested changes (marquee implementation, formatting, and added the newline at end of file).
Could you please take another look and re-run the CI checks when you get a chance?
Thanks!

[adhiamboperes]

Thanks @anmoltrvd01! This solution is now in the correct direction. Could you please do the same to the rest of teh activities under "PR 11: Settings & Help" so that we can mark the checkbox as completed when your PR is merged?

However, please note that because this PR was force-pushed, you need to create a duplicate PR and copy both your changes and the nicely written PR description(including the before/after evidence).

In the wiki, force-pushing is prohibited because it changes the revision history. Only use merge and not rebase, and if you change something in your code, just create a new commit since you cannot ammend any that has been pushed already.

[anmoltrvd01]

Hi @adhiamboperes,
Thank you for the guidance. As suggested, I created a new PR without force-push history and copied the updated changes and PR description (including the testing evidence and recordings).

New PR: #6135

This new PR includes the marquee implementation and verification for all fragments under PR 11: Settings & Help with 200% font scaling. Please let me know if any further changes are needed.
Thank you!