[GH-ISSUE #967] Fix glossary.csv #3701

Closed
opened 2026-03-13 12:40:39 +03:00 by kerem · 6 comments
Owner

Originally created by @itagagaki on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/967

Originally assigned to: @VShawn, @itagagaki on GitHub.

The regression caused by #907 must be resolved.

Originally created by @itagagaki on GitHub (Aug 10, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/967 Originally assigned to: @VShawn, @itagagaki on GitHub. The regression caused by #907 must be resolved.
kerem 2026-03-13 12:40:39 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@VShawn commented on GitHub (Aug 11, 2025):

As the project scales up, I've found that it's easy for text errors to occur in a single vocabulary list. So I am considering restructuring the vocabulary to reduce the probability of editing errors.

<!-- gh-comment-id:3174264533 --> @VShawn commented on GitHub (Aug 11, 2025): As the project scales up, I've found that it's easy for text errors to occur in a single vocabulary list. So I am considering restructuring the vocabulary to reduce the probability of editing errors.
Author
Owner

@itagagaki commented on GitHub (Aug 12, 2025):

That would be better.
For now, it's necessary to correctly re-merge the Italian and subsequent changes. Shall I do it?

<!-- gh-comment-id:3178825933 --> @itagagaki commented on GitHub (Aug 12, 2025): That would be better. For now, it's necessary to correctly re-merge the Italian and subsequent changes. Shall I do it?
Author
Owner

@VShawn commented on GitHub (Aug 13, 2025):

Actually, I have already made the repairs(#969) with AI. Perhaps you could help me double-check it.

<!-- gh-comment-id:3182469930 --> @VShawn commented on GitHub (Aug 13, 2025): Actually, I have already made the repairs(#969) with AI. Perhaps you could help me double-check it.
Author
Owner

@itagagaki commented on GitHub (Aug 15, 2025):

Leave the corrections to me.
#969 probably has a different base. Not only is the Japanese restoration is incomplete, but it also uses different keys for some terms, which affects the everything.

<!-- gh-comment-id:3190440462 --> @itagagaki commented on GitHub (Aug 15, 2025): Leave the corrections to me. #969 probably has a different base. Not only is the Japanese restoration is incomplete, but it also uses different keys for some terms, which affects the everything.
Author
Owner

@VShawn commented on GitHub (Aug 16, 2025):

okey, the ticket is your now.

<!-- gh-comment-id:3193090010 --> @VShawn commented on GitHub (Aug 16, 2025): okey, the ticket is your now.
Author
Owner

@itagagaki commented on GitHub (Aug 18, 2025):

Fixed by #970

<!-- gh-comment-id:3197195976 --> @itagagaki commented on GitHub (Aug 18, 2025): Fixed by #970
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/1Remote#3701
No description provided.