winapps-org/winapps

Failed to parse detected application contained a Japanese named applcation

Open

#457 opened on Mar 13, 2025

View on GitHub
 (6 comments) (5 reactions) (0 assignees)Shell (463 forks)batch import
good first issuehelp wanted

Repository metrics

Stars
 (15,020 stars)
PR merge metrics
 (Avg merge 12h 59m) (3 merged PRs in 30d)

Description

I tried to install winapp, but the installing process was stopping at parse detected applications.

I report error log and my enviroment. Applications using CKJ Font probaby will occur a parsing error.

Error log

Creating an application entry for cmd... Done!
Creating an application entry for access... Done!
Creating an application entry for excel-o365... Done!
Creating an application entry for onenote-o365... Done!
Creating an application entry for outlook-o365... Done!
Creating an application entry for powerpoint-o365... Done!
Creating an application entry for publisher-o365... Done!
Creating an application entry for word-o365... Done!
/home/teru/.local/share/winapps/detected: 行 67: 対応する ``' を探索中に予期しないファイル終了 (EOF) です
Exiting with status '1'.
  • /home/teru/.local/share/winapps/detected: 67
NAMES+=("タッチ キーボードと手書きパネル")

My enviroment

Contributor guide

Research direction
Trace the script that generates the detected applications list inside the VM, and locate where Japanese characters cause a shell parsing error. Apply proper quoting or escape sequences to handle non ASCII characters.
Tech stack
shell
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ShellGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75