Skip to content

feat: Add LFW and Four-corner input methods with UI fixes and layout adjustments - #9

Open
hubpixie wants to merge 4 commits into
tinbreaker:mainfrom
hubpixie:main
Open

feat: Add LFW and Four-corner input methods with UI fixes and layout adjustments#9
hubpixie wants to merge 4 commits into
tinbreaker:mainfrom
hubpixie:main

Conversation

@hubpixie

Copy link
Copy Markdown

Description

This pull request introduces significant improvements to the input methods and user interface of the Tangut Script Annotation Tool.

Key Changes

  1. New Input Methods:

    • Added support for LFW (Li Fanwen) numbers and Four-Corner codes alongside the existing Unicode radical input. This addresses the inefficiency of character-by-character input, enabling practical and much faster search speeds.
    • Cleaned up and updated input placeholders to guide users clearly.
  2. UI & Layout Fixes:

    • Unified the background colors of all clear buttons for consistency.
    • Fixed the stroke button hover state to properly invert the image color to white (brightness(0) invert(1)).
    • Adjusted the PC layout to prevent overflow, aligning it cleanly with the mobile-friendly styling.

Testing

  • Verified that LFW numbers and Four-Corner codes correctly query and display target characters.
  • Checked clear button and stroke button hover behaviors across viewports.
  • Confirmed responsive layout consistency between PC and mobile screens.
feat-20250815

hubpixie added 2 commits August 15, 2026 12:36
…dition to Unicode radicals

- Add LFW number and Four-Corner code input methods to achieve practical input speeds, as the current Unicode radical input is inefficient (character by character)
- Clean up and update input placeholders
- fix(ui): unify clear button colors, fix stroke button hover color for images, and adjust PC layout to prevent overflow matching mobile styling
@tinbreaker

Copy link
Copy Markdown
Owner

I've tested your PR, but the four-corner code method requires the L0000 format to be effective. I also found that the LFW output contains a superscript “L,” which is neither in my database nor compliant with scholarly standards. Would you please fix this? Thanks!

hubpixie added 2 commits August 29, 2026 15:55
…t output

- Refine input validation logic for "L" prefix (max 4 digits, L0000 format), numeric input (max 6 digits), and restrict numbers when starting with non-L characters
- Remove extraneous superscript "L" from LFW output strings to comply with scholarly standards
- Align the order of Four-Corner codes in the output
@hubpixie

Copy link
Copy Markdown
Author

Hi,

Thank you for the review and for pointing out the issues with the L0000 format and the superscript "L" in the LFW output.

I have pushed a new commit addressing all of your feedback:

  • Refined the input validation logic to properly support the L0000 format (up to 4 digits for "L" prefixes), restricted numeric inputs to a maximum of 6 digits, and restricted numbers when starting with non-L characters.
  • Removed the extraneous superscript "L" from the LFW output strings to comply with scholarly standards.
  • Aligned the order of the Four-Corner codes in the output.

Could you please take another look at the PR when you have a moment? Thanks again for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants