Alternative sprites for RTL language suppot

Open
#405 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reading grfcodec PR #46 and OpenTTD PR #14188 to understand how alternative RTL sprites are represented. Then locate NML's sprite-info encoding and determine where bit 4 must be supported; done means NML can emit this flag for alternative sprites.

Written by the indexing model from the issue text.

Description

Grfcodec now (https://github.com/OpenTTD/grfcodec/pull/46) and OpenTTD will presumably soon (https://github.com/OpenTTD/OpenTTD/pull/14188) support alternative sprites for RTL languages, for example a left-pointing fast-forward or play button make more sense in RTL languages. This is encoded in bit 4 in the sprite info byte.

NML support would be appreciated!

Dominant language
Python
Stars
61
Forks
47
Avg merge
8d 14h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 OpenTTD/nml

All issues in OpenTTD/nml

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.