mercari/engineer-vocabulary-list

Engineer Vocabulary List in Japanese/English

engineer-vocabulary-list's Issues

「チケットを取る」 is not an appropriate usage in Japanese

IMO, 「チケットを取る」means to purchase or reserve a ticket for a concert or a flight.

If we mean "take an issue" in an issue tracking system, a normal Japanese verb would be
「チケットを引き受ける」or 「チケットを着手する」

Why don't we have the primary source as a single text file (like csv or tsv) ?

First, thank you for this great innovation.
This work is valuable for the whole industry.

I have a suggestion.
Why don't we have the primary source as a text file (like csv or tsv) ?

• A text file can be easily converted into any forms (pdf, xlsx, html, etc). If we had it as a single text file, we would not need to maintain duplicate resources
• A text file would be more machine readable and machine friendly. It would be more natural for engineers and open source community. https://en.wikipedia.org/wiki/Unix_philosophy
• If we had it as a text file, contribution by a pull request would be much more easier.

Add "ログインできました"

IMO, one of the most common mistakes for Japanese speakers is the usage of "could".

I have seen many Japanese people say:

• I could login (for ログインできました)
• I could buy the item (for 商品を購入できました)

But actually these usage of "could" sound like subjunctive, right ?

So I would suggest we add this case to the list.

• I was able to login / I successfully logged in (for ログインできました)

List #1-16 example sentence for "obstacle, hitch" doesn't match

the example sentence for 1-16 "支障 = obstacle, hitch" uses "interfere" instead of "obstacle" nor "hitch".

It interferes with it (our project).