how about using 文言 as another extension name
Good suggestion!
It seems that the OS (at least on my computer) is fine with unicode file extensions. So there's no reason we can't have that
Perhaps we can even use 書、經、章、篇 etc as file extensions.
I'll consider adding it in the README as a suggestion to users and plugin-writers.
How about a file name without extensions? Actually as you mentioned above, the "書", "經", "章", "篇" actually could be the extension meaning in their filename :)
How about a file name without extensions? Actually as you mentioned above, the "書", "經", "章", "篇" actually could be the extension meaning in their filename :)
Extensions are needed because they play a crucial role in file sorting.
How about "简" "帛" "铭", while they can also appear in filename, maybe ".文言" is still best.
VScode extension author here. Just saw this issue and I am interested in it.
I have done some test, Unicode extension names and files without extensions (end with "書", "經", "章", "篇" without dot) seems to work fine with VSCode. (not sure for sublime and vim etc)

When this is settled, I would love to ship it!
我是 vim 重度用户,我把 *.文言 后缀识别也加到 vim 插件了。
但是暂不想加没有后缀的 "書", "經", "章", "篇" ,这个不一定确认它就是 wenyan-lang 脚本了。
或许可以再根据文件前几行内容来猜测文件类型。
比如在 unix/linux 中支持如下自执行脚本的语句:
#!/usr/bin/env wenyan
然而这行声明放在开头也很诡异出戏。
https://github.com/lymslive/vim-wenyan
fork from https://github.com/voldikss/vim-wenyan
已 pr
虽然我自己在使用 vim 尝试 wenyan-lang 时可能还有意加不少扩展功能,但不想重复另建仓库,也懒得想仓库名字了。
然后,既然脚本名后缀允许.文言 了,wenyan-lang 是不是也可以约定一个中文名字,类似“易语言”。
直接叫“文言语言”吗?有没更好听的。
I think if this language should have a Chinese name, a problem would be should we take this language as the only language in ancient China? If the answer is yes the name of the language can be like 硅机速算术 or something like that; If the answer is no... I can't come up with a good name.
Most helpful comment
Good suggestion!
It seems that the OS (at least on my computer) is fine with unicode file extensions. So there's no reason we can't have that
Perhaps we can even use 書、經、章、篇 etc as file extensions.
I'll consider adding it in the README as a suggestion to users and plugin-writers.