User Tools

Site Tools


doc:en:importingglyphs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:en:importingglyphs [2013/02/01 11:53]
rosmord [Attaching codes to drawings, and inserting them in JSesh]
doc:en:importingglyphs [2022/01/12 09:53] (current)
dmorandi [Attaching codes to drawings, and inserting them in JSesh]
Line 7: Line 7:
 In the "Font Selection"​ tab (currently the only one available), enter the folder you want to use in the "​Hieroglyphic font directory"​ field. You should create an empty folder for this specific purporse. In the "Font Selection"​ tab (currently the only one available), enter the folder you want to use in the "​Hieroglyphic font directory"​ field. You should create an empty folder for this specific purporse.
  
-Creating a folder ​+{{ http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​glyphDir1.png |Creating a folder}}
  
-The Folder is Selected+{{ http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​glyphDir2.png |The Folder is Selected}}
  
-You only have to do this once. Next invocations of JSesh will use this folder. 
  
 +You only have to do this once. Next invocations of JSesh will use this folder.
 ===== Actual sign insertion===== ===== Actual sign insertion=====
  
Line 22: Line 22:
   * you assign a code for each sign you have imported, and then you insert the new sign in the JSesh list of signs.   * you assign a code for each sign you have imported, and then you insert the new sign in the JSesh list of signs.
  
-New signs importing interface+{{ http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​importSigns1.png |New signs importing interface}}
 ==== Importing drawings ==== ==== Importing drawings ====
  
  
 Importing drawings is easy. JSesh can read: Importing drawings is easy. JSesh can read:
- * true type fonts  +  ​* true type fonts  
- * .tml and bzr files, which can be created with JSesh'​s forerunner, tksesh.  +  * .tml and bzr files, which can be created with JSesh'​s forerunner, tksesh.  
- * SVG files+  * SVG files
  
 Simply click on the "​import file" button, and select the file which contains your picture(s). You can use the navigation buttons (those with arrows) to browse the available signs. Simply click on the "​import file" button, and select the file which contains your picture(s). You can use the navigation buttons (those with arrows) to browse the available signs.
Line 37: Line 37:
 In some cases, the size or orientation of your signs won't be correct. For instance, in the picture below, the duck is too large and its orientation is wrong. In some cases, the size or orientation of your signs won't be correct. For instance, in the picture below, the duck is too large and its orientation is wrong.
  
-Fine Tuning+ 
 +{{ http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​importSigns2.png |Fine Tuning}}
  
 You can correct this : You can correct this :
-  * the buttons ​ and  can be used to change the sign orientation;​+  * the buttons ​{{http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​importSigns3.png}} ​and {{http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​importSigns4.png}} ​can be used to change the sign orientation;​
   * the button "Full cadrat height"​ gives the sign the same size as the A1 sign;   * the button "Full cadrat height"​ gives the sign the same size as the A1 sign;
   * if you click on the sign's window and drag the mouse, the mouse position will set the sign's height.   * if you click on the sign's window and drag the mouse, the mouse position will set the sign's height.
- 
 ==== Attaching codes to drawings, and inserting them in JSesh ==== ==== Attaching codes to drawings, and inserting them in JSesh ====
  
Line 50: Line 50:
 Except when you are creating signs which are already documented in the Manuel de Codage (for instance, because they are not available in JSesh), you should first get a user ID, which will differentiate your signs from the signs created by other users. Except when you are creating signs which are already documented in the Manuel de Codage (for instance, because they are not available in JSesh), you should first get a user ID, which will differentiate your signs from the signs created by other users.
  
-to get an uid, send an email to < rosmord@iut.univ-paris8.fr > . Note for tksesh users: the uid is simply your tksesh id.+to get an uid, register as JSesh user. Note for tksesh users: the uid is simply your tksesh id.
  
 Be carefull when giving signs a name. You want your files to be readable by anyone, so be faithfull to the "​Manuel de codage"​. Our current suggestions are the following: Be carefull when giving signs a name. You want your files to be readable by anyone, so be faithfull to the "​Manuel de codage"​. Our current suggestions are the following:
  
-  * If you create your own version of a sign in the Manuel (either because it isn't available in JSesh yet, or you don't like the default sign provided, use either the standard Manuel de codage for the sign, or use the following notation: ​US uid gardiner ​code, where uid is the user id. +  * If you create your own version of a sign in the Manuel (either because it isn't available in JSesh yet, or you don't like the default sign provided, use either the standard Manuel de codage for the sign, or use the following notation: ​USuid Gardiner ​code, where uid is the user id. 
-  * When you create a sign which you consider as a variant of a standard sign, you should build its name like that: USuid+Gardiner Code+"​VAR"​+VARIANT CODE where : Gardiner Code is the standard Manuel de codage code for the base sign and VARIANT CODE is usually an uppercase ​le. \\ The Ramesside usual form for the hare has a Seth animal tail. If I want to distinguish it from the "​normal"​ sign, I can call it US1E34VARA. +  * When you create a sign which you consider as a variant of a standard sign, you should build its name like that: USuid+Gardiner Code+"​VAR"​+VARIANT CODE where : Gardiner Code is the standard Manuel de codage code for the base sign and VARIANT CODE is usually an uppercase ​letter. \\ The Ramesside usual form for the hare has a Seth animal tail. If I want to distinguish it from the "​normal"​ sign, I can call it US1E34VARA. 
-  * When the sign you create corresponds to a completely new sign, give it a code of the form: USuid+Gardiner Category + NUMBER +"​XT"​+OPTIONNAL ​VARIANT CODE. \\ You are free to choose the number you like, but I would suggest you try to find a logical layout. It would also be better if this number does not correspond to a "​standard"​ sign (to avoid confusing innocent users of other softwares), So you can for instance start your numbering at 1000. Note also that the number should not contain leading zeros. The Category should be correct, and if you really don't have a clue, you should use the Aa category. "​Ff"​ is reserved for signs used specifically when transcribing hieratic.\\ Example : the Harp Louvre E 116 A has recently been published by C. Barbotin (La voix des hiéroglyphes,​ p. 66-67), and in its text appears the unknown sign . I can create this sign, and give it, for instance, the code US1Aa1000XT. On the other hand, the Israel Stela contains a sign which is most probably a griffin, but does not correspond to any registered griffin sign in the manuel. So I gave it the code US1E162VARA,​ because E162 is a griffin sign.+  * When the sign you create corresponds to a completely new sign, give it a code of the form: USuid+Gardiner Category + NUMBER +"​XT"​+OPTIONAL ​VARIANT CODE. \\ You are free to choose the number you like, but I would suggest you try to find a logical layout. It would also be better if this number does not correspond to a "​standard"​ sign (to avoid confusing innocent users of other softwares), So you can for instance start your numbering at 1000. Note also that the number should not contain leading zeros. The Category should be correct, and if you really don't have a clue, you should use the Aa category. "​Ff"​ is reserved for signs used specifically when transcribing hieratic.\\ Example : the Harp Louvre E 116 A has recently been published by C. Barbotin (La voix des hiéroglyphes,​ p. 66-67), and in its text appears the unknown sign <image missing>. I can create this sign, and give it, for instance, the code US1Aa1000XT. On the other hand, the Israel Stela contains a sign which is most probably a griffin, but does not correspond to any registered griffin sign in the manuel. So I gave it the code US1E162VARA,​ because E162 is a griffin sign.
   * Using this system when importing texts from other softwares: it is possible that other softwares provide their own "non standard"​ codes. If you want to import texts from those software into JSesh, you might need to give a name to the new signs they contain (note that fonts are usually protected by copyright laws, so you will need to redraw the signs yourself, either by adaptating existing JSesh signs or by finding a picture of the signs in original hieroglyphic sources). For compatibility purposes, the following user codes can be used for other softwares: winglyph 1000 macscribe 1001 inscribe 1002 got 1003 visualglyph 1004 If you think of other softwares I should add, please tell me.   * Using this system when importing texts from other softwares: it is possible that other softwares provide their own "non standard"​ codes. If you want to import texts from those software into JSesh, you might need to give a name to the new signs they contain (note that fonts are usually protected by copyright laws, so you will need to redraw the signs yourself, either by adaptating existing JSesh signs or by finding a picture of the signs in original hieroglyphic sources). For compatibility purposes, the following user codes can be used for other softwares: winglyph 1000 macscribe 1001 inscribe 1002 got 1003 visualglyph 1004 If you think of other softwares I should add, please tell me.
   * standard manuel de codage code. You will find these codes in Hannig'​s WB, for instance. A number of lists are also available on the web. Please, note that using the codes is one thing, but that the actual signs drawing in the fonts of other softwares are legally protected. So, have to come with you own versions of the signs, either from actual sources or by re-creating them. You will find more information on signs drawing in the next section. In our example, your duck would replace the normal one, so it would have code "​G39"​.   * standard manuel de codage code. You will find these codes in Hannig'​s WB, for instance. A number of lists are also available on the web. Please, note that using the codes is one thing, but that the actual signs drawing in the fonts of other softwares are legally protected. So, have to come with you own versions of the signs, either from actual sources or by re-creating them. You will find more information on signs drawing in the next section. In our example, your duck would replace the normal one, so it would have code "​G39"​.
Line 63: Line 63:
 Note that for compatibility with tksesh, we also support arbitrary "user glyph codes"​. These codes correspond to the codes tksesh gave to new signs. User glyph codes have the form UG id M mid N sid , where id, mid, and sid are numbers. Avoid using those codes for now. Note that for compatibility with tksesh, we also support arbitrary "user glyph codes"​. These codes correspond to the codes tksesh gave to new signs. User glyph codes have the form UG id M mid N sid , where id, mid, and sid are numbers. Avoid using those codes for now.
  
-Figure 6.4. Inserting the duck sign as UG1M2N0 
- 
-Inserting the duck sign as UG1M2N0 
  
-When your sign is ready, click on the insert button.+{{ http://​jsesh.qenherkhopeshef.org/​files_jsesh/​images/​importSigns5.png |Inserting the duck sign as UG1M2N0}}
  
 +When your sign is ready, **click on the insert button**.
 ==== Alternative system for sign insertion ==== ==== Alternative system for sign insertion ====
  
 If your sign SVG file has a name which corresponds to a code (say, US1A1VARA.svg),​ and the quadrant module is either 18px or 1800px, than you can simply put the sign in your hieroglyphic folder. If your sign SVG file has a name which corresponds to a code (say, US1A1VARA.svg),​ and the quadrant module is either 18px or 1800px, than you can simply put the sign in your hieroglyphic folder.
  
doc/en/importingglyphs.1359715996.txt.gz · Last modified: 2016/10/12 14:14 (external edit)