Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] New or heavily modified features do not have proper localisations

Open
#4 0 comments 0 reactions 2 assignees View on GitHub

Maintainers usually reply within 1 day

@timi2506 is already working on this.

Since Jan 19, 2025.

Assessment

This issue has not been assessed yet.

Description

bug help wanted

Some features, mostly new or heavily modified ones, lack proper localisations (including English). As a result, Twitter displays translation keys instead. For example, instead of the intended text like "Member" on a Community Tweet, it'll display COMMUNITY_TWEET_MEMBER_BADGE_LABEL.

This issue occurs because of missing language strings, as NeoFreeBird currently relies on the localisation files from the latest Twitter-branded app, which is a few years old.

This means we need to:

  1. Decompress the localization files.
  2. Compare NeoFreeBird's files with the latest Twitter/X app version.
  3. Integrate the new keys and strings while reverting any X branding to Twitter, including replacing "Post" with "Tweet."

Current language support:

  • English
  • Swedish

If your language is not translated, it'll default to English instead of showing THE_TRANSLATION_KEY. For languages that do not use the Latin alphabet, the process may take longer, but we aim to ensure compatibility for all languages over time.

[!NOTE]
Since we don't speak most of Twitter's supported languages, we can't guarantee that all "Post" → "Tweet" translations will be grammatically perfect. However, all old branding from the last Twitter app will be kept, so only new features will require adjustments. If your language isn't grammatically correct, please help us out and create a Pull Request!

Dominant language
Objective-C
Stars
1.7k
Forks
133
Avg merge
13h 24m
Merged PRs (30d)
13

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoFreeBird/app

All issues in NeoFreeBird/app

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.