W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2005

[ESW Wiki] Update of "its0908LinguisticMarkup" by GoutamSaha

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 29 Sep 2005 02:44:42 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050929024442.32702.90004@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by GoutamSaha:
http://esw.w3.org/topic/its0908LinguisticMarkup


------------------------------------------------------------------------------
  ie. please focus on technical content, rather than wordsmithing at this stage.
  
  
- Author:  '''Goutam Kumar Saha'''
+ '''Author:  Goutam Kumar Saha'''
  
  
  = Linguistic Markup =
@@ -39, +39 @@

            not find any difficulty in marking up such language specific information.
            It is not mendatory for an author to add finer classified metadata at all.
            He/she has to add metadata at some parts of his/her content which are
-           exceptionally special with respect to his/her source language aspects.]] 
+           exceptionally special with respect to his/her source language aspects.
+ 
+           For example: for the Phrases_Idioms "cats and dogs" in english we can markup as
+           <sentence_cat name="phrases_idioms" meaning="heavily"> cats and dogs
+           </sentence_cat> 
+           Such metadata will be of an immense help to localazation process (in order
+           to find an appropriate phrases & idioms in a target language) without
+           even knowing the source language- english well. 
+ 
+           Similarly, in Bangla- source language, for the phrases & idioms say,
+           " Dumurer (english meaning is Fig's)  Fool (english meaning is Flower)"
+           we can markup as
+           <sentence_cat name="phrases_idioms" meaning="rarely visible">
+           Dumurer Fool </sentence_cat> 
+           
+           Such metadata is very useful as a semantic markup to a localization process,
+           irrespective of a target language. ]] 
     
  Metadata information about the domain, sentence type or specific words
  will help translators to do better quality work or to do the work quickly.
  If translators know that a word belongs to a specific domain then they can go to a 
  terminoloy data base and check the word,  thus, even for human translators this 
  3-Tier or 3-layer schema will be helpful. One cannot do an accurate translation
- without such information.  
+ without such information. 
+  
  For example: 
- 
  <content_domain name="factory">
  Paul works in a factory. 
  There are many electromechanical machines in this factory.
- ---- sentence_i
+ ...sentence_i
     Give  <pos_cat name="noun" type="material"> oil </pos_cat> .
- ----- sentence_k
+ ...sentence_k
  </content_domain>
- 
+ =====
  <content_domain name="office">
-    Paul works in a government office.  He advices a new employee. 
+    Paul works in a government office.  He advises a new employee. 
-   <pos_cat name="verb" type="joining" meaning="praise"> Give oil </pos_cat> 
+   <pos_cat name="verb" type="joining" meaning="please"> Give oil </pos_cat> 
      to your senior.
-   <!--such information via attributes aim to provide semantic as well as language specific transformation constructs to a translator-->
+   <!--such information via attributes aim to provide semantic as well as language
-      ----- sentence_m
+       specific transformation constructs to a translator-->
+ ...sentence_m
  </content_domain>
  
  
Received on Thursday, 29 September 2005 11:00:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:45 GMT