Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

第七第八用字疑義 #21

Open
747 opened this issue Aug 2, 2020 · 6 comments
Open

第七第八用字疑義 #21

747 opened this issue Aug 2, 2020 · 6 comments

Comments

@747
Copy link

747 commented Aug 2, 2020

維天地生人之初。茹毛飲血而衣皮葦。所以異於禽獸者幾稀。而自三代以降。其去禽獸之日遠。其文明之愈盛。何邪。得無言語之益乎。夫嗚嗚然。啾啾然。狺狺然。奔走而吿其黨者。此禽獸之言語也。然上治萬乘之國。牧天下之民。下鑄析革之兵。造罟耨之具。皆非其嗚嗚然。啾啾然。狺狺然可以傳也。不能傳者。父偶得之。子偶失之。子偶知之。孫偶忘之。是故智巧之萌。自言語始。倉頡造字。天雨粟。鬼夜哭。所泣者何。洩天地之機也。先賢言語既見於書。後人欲有所建。豈必起於平地。但添一瓦於鴻基。而郁郁乎廣廈日成矣。西哲牛頓曰。或有異吾之遠見者。無他。但立巨人肩耳。是理也。故易繫辭曰。上古結繩而治。後世聖人易之以書契。百官以治。萬民以察。

竊未嘗聞析革一詞,檢之於經典中不得,纔見「金革」義稍近。子其知是詞何謂乎?

回文者。順逆讀之皆成韻文者也。漢有鏡銘。蘇蕙有璇璣圖。晉以降作者甚眾。而東坡尤工之。今作是程序。因其順而得其逆。因其逆而得其順。以示諸法之用。

程序一詞初見焉,以後或與程式混用。此二者便有何異同?

抱朴。參同。萬畢。古之方術書也。周髀。九章。海島。古之算術書也。孫吳。三略。六韜。古之兵術書也。術者竟何。成法也。夫人之初任一事。有成有敗。或得或失。卒不知孰為可法。君子仰觀前人之殷鑒。俯羅不易之步驟。法象萬物。為法為道。名之曰術。後人循之遵之。成事因之。故韓非子曰。人主之所执也。

文本首句為抱朴,成書乃作「樸」。尾句曰所执也,亦形「執」。皆似字模訛舛也。而按前者原文「朴」通「樸」,猶可也。後者「执」唯今世之簡字,當改耳。

image image

又凡循環皆可作遞歸解。遞歸皆可作循環解。但擇其易敘者而為之也。譬客有問行百步之法者。一曰。百遍為之而行一步。是行百步也。此循環也。一曰。先行一步。復行其餘九十九也。若問何以行其九十九耶。則先行一步。復行其九十八步也。此遞歸也。例曰。莊子云。一尺之錘。日取其半。萬世不竭。今既十日。問其錘長。

一尺之錘,按應作「棰」字,今本『莊子』如此。棰,木杖也。錘,金棒也。斷錘為半,不知其難何如。後復有一處並同。

吾學甚淺,不免有蜀犬吠日之非,請君恕諒。

@LingDong-
Copy link
Member

Hi @747,

Thanks so much for pointing out these errors! I've fixed them in commit a56c27e

  • 棰、执 -- totally my mistake, now fixed.

  • 朴 -- it seems like in the particular case of the book title 抱朴子, 朴 is more often written instead of 樸. Example.

  • 程序、程式 -- they're synonyms, I've now changed the former to the latter in later chapters for consistency.

  • 析革 -- I've actually forgotten why I ended up using the phrase (it's been a while :). I think I wanted to mean weapons [兵] that cut/break [析] leather (armour) [革]. But you're right, I couldn't find another source that uses 析 this way. However 金革之兵 also feels weird, since 金革 originally means "weapon and armour" which is redundant with 兵. After some consideration I've changed it to 達革之兵, taken from "南山有竹,不柔自直,斬而用之,達於犀革⋯⋯"(論語), to ensure correct usage.

Thanks again for finding so many mistakes! Very much appreciated.

@747
Copy link
Author

747 commented Aug 5, 2020

@LingDong- 微勞有助,不勝榮幸。

  • 朴 -- it seems like in the particular case of the book title 抱朴子, 朴 is more often written instead of 樸.

是乃「执」「執」之鏡像也。今閱網頁,是字依然貌肖「樸」,如上圖。文本既為範,則彼字體必乖違其意。

此外,字體是否缺失「央」字字模?
image

@747
Copy link
Author

747 commented Aug 8, 2020

「棰」字亦未備也。
image

@LingDong-
Copy link
Member

Hi @747

Thanks for spotting the missing glyphs! I've now fixed them.

Snip20200808_39

Snip20200808_40

( The reason for the missing glyphs was that, to make the webpage load faster, only characters used by the book are included in a special "truncated" font. Since the new changes brought characters not used previously, the font has to be regenerated, which I just did :)

@747
Copy link
Author

747 commented Aug 10, 2020

切謝作者。今復省上述諸條,有二所未見改矣。姑問,其有意否?

  • 「朴」字之形仍相齟齬(例如「抱朴」)

    image
    (蓋此於原字體,所以避簡繁之賸弊也,然在本書中,只使之失正耳。奈何。)

  • 程序雖已除於第九以降,仍存於第七第八中,共二處

回文者。順逆讀之皆成韻文者也。漢有鏡銘。蘇蕙有璇璣圖。晉以降作者甚眾。而東坡尤工之。今作是程序。因其順而得其逆。因其逆而得其順。以示諸法之用。

乃得七。八。二諸數。參不同。而一術蔽之。不亦易乎。故曰。凡用非一。皆當術之。斯亦所以令程序明練可讀。如文章之命篇者也。又或改易一處。則施者皆不易而易矣。故曰術者雖非必有。然欲以程式立大事者。用術乃不可不精也。

@LingDong-
Copy link
Member

Hi @747

  • 程序→程式 now fixed: 07b3a22

  • 樸: Sorry I forgot to address this point in my last comment. The issue is caused by the strategy used by the custom font. Often times the font only has one variant form of a character so it tries to fill other forms with the one it has, in order to cover most glyphs in unicode. Though possible, it would be somewhat inconsistent to make exceptions for one particular case like this. And I also feel that even though 抱樸子 is not as accurate as 抱朴子, it's still kinda bearable.

Thanks again for spotting the mistakes!

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

No branches or pull requests

2 participants