Add square bracket notation for concatenated Morse code transmission #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements support for square bracket notation
[...]to send Morse code characters without inter-character spacing, addressing the need to transmit character combinations like[AR]and[ホレ]as single concatenated patterns.Problem
In Japanese and European Morse code, certain character combinations are sometimes transmitted as continuous patterns without the standard inter-character spacing. For example:
ARis normally sent as.- .-.(with space between A and R)[AR]should be sent as.-.-(concatenated without space)ホレcan similarly be concatenated as[ホレ]Solution
The implementation adds bracket parsing to the
get_morse_str()function:[...]patterns in input stringsExamples
Key Features
The generated audio files confirm the implementation works correctly - bracketed versions produce shorter audio due to eliminated inter-character spacing.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.