你好,
我為 Wycliffe 專案填寫這些資訊,以下是我們的做法:
*本地化全名:語言社群的名稱。
*本地化描述:語言社群的名稱後接正典範圍(聖經、新約、部分經文)
您可以將「本地化描述」留空。
*縮寫:應該是 ISO 代碼(可在「基本」分頁中語言名稱後找到)
*本地化縮寫:如果有幾個方言使用相同的 ISO 代碼,則在 ISO 代碼後加上分隔符。例如,有 5 種 Huave 語言,所以我會寫 huvJ(代表 Jucitan)、huvSM(代表 San Mateo)。這些可能不會與 Paratext 的短名稱匹配,但應該使用拉丁文字,因為它們是為了方便 DBL 出版商使用。
*受眾與文本讀者的教育程度有關。我們幾乎對所有文本使用「通用」。如果它是專門為兒童設計的聖經,您應該使用「兒童」。如果它是「易讀版」聖經,您可能希望使用「基礎」。
*「媒體」欄位是用來定義文本將如何分享的。對於 DBL,它將是「電子」。如果您計劃授權給 FCBH 製作音訊檔案,則也會是「音訊」。
*「推廣文字」會顯示在數位出版商應用程式的「頁面」底部。因此,如果您有一個希望人們前往以獲取更多資訊的網站,這是一個放置該資訊的好地方。
Hi,
I complete this information for Wycliffe projects, and this is what we do:
*Localised Full Name: Name of the Language Community.
*Localised Description: Name of the Language Community followed by Canon (Bible, NT, Portion)
You can leave the Localised Description blank.
*Abbreviation: should be the ISO code (found on the Basic tab following the Language)
*Localised Abbreviation: ISO code followed by a delimeter if there are several dialects that use the same ISO. For example, there are 5 Huave languages, so I would put huvJ (for Jucitan), huvSM (for San Mateo) These will probably not match the Paratext Short Name, but should be in Latin script, as they are for the benefit of DBL publishers.
*Audience has to do with the education level of the readers of the text. We use “Common” for almost every text. If it is specifically a children’s bible, you would to use "Children. If it is an “easy read” Bible, you may want to use “Basic”.
*The Media field is where you define how the text is going to be shared. For the DBL, it will be Electronic. If you plan to license it to FCBH for audio files, it will be Audio as well.
*The Promotion Text will show up in digital publishers’ apps at the bottom of a “page”. So, if you have a website you would like people to be directed to for more information, this is a good place to put it.
機器翻譯自 English