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

Customer is requesting Nemeth Block Indicators to work as they did in version 2, as opposed to version 3

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin
Domain
desktop

Research direction

The issue names no files or tests. Start by reading the current Nemeth block indicator behavior and comparing it with version 2, then identify where a user preference could select between the two behaviors. Done means users can choose either behavior, including the current version 3 behavior and the version 2 behavior requested for numbered blocks of math problems.

Written by the indexing model from the issue text.

Description

This is from feedback from a customer that reached out to our customer service department. The feedback was this: They would like the Nemeth block indicator function to work the way it did back in version 2, as opposed to how it works now in version 3. They say that the way it works in version 3 is great for something such as word problems or a document containing mixed text and numbers, but that the way it was set up to work in BB v2 worked better for a block of math problems where each problem in the set is numbered. They wondered if the developers might consider making it a preference where you could choose which way the Nemeth block indicator worked, as it does now in v3, or as it used to work in v2.

Dominant language
Kotlin
Stars
15
Forks
11
Avg merge
13h 16m
Merged PRs (30d)
9

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 aphtech/brailleblaster

All issues in aphtech/brailleblaster

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.