Re: [xliff] XLIFF Teleconference Details & Agenda - Tuesday,21 Jan 2003

Hi Mirek: 

 

Thanks for your suggestion.  I'm not tearing 
it apart,  and maybe I'm not fully understanding your suggestion,  but 
I'm not sure that we need to add the 
attribute "for-group" since we can specify these attributes at the 
<group> level - no?  Doing so would set 
those attribute values as default for any trans-unit within the scope 
of the entire group,  with override possible by specifying the 
attribute value at the trans-unit or target..

 

Therefore, couldn't we express your 
example as follows without adding a new attribute, and without the unnecessary 
group for the dialog?   Or have I gotten it all terribly 
wrong?

 

...

<group font="MS Sans Serif;8" style="WS_POPUP 
| WS_CAPTION | WS_THICKFRAME">

    <trans-unit id="DIALOG1" coord="0;0;96;28"

        
<source/>

        <target phase-name="after_resizing" 
coord="0;0;96;28">    -- local version of dialog 
coordinates

        
</target>

    </trans-unit>

    <trans-unit id="IDC_EDIT1" 
coord="35;7;53;14">

       <source/>

        <target phase-name="after_resizing" 
coord="40;7;60;14">    -- local version of editbox 
coordinates

        </target>

     </trans-unit>

     <trans-unit id="IDCSTATIC" 
coord="13;9;23;8">

        <source>Label:</source> 

        <target phase-name="after_resizing" 
coord="25;9;35;8">         -- local version 
of label coordinates

   
         Translated 
Label:           

        
</target>

     </trans-unit>

</group>

 

Cheers,

Tony

 

  
----- Original Message ----- 

  
From: 
  Mirek 
  Driml 

  
To: 'Tony Jewtushenko' ;  

  
Sent: Monday, January 20, 2003 10:59 
  AM

  
Subject: RE: [xliff] XLIFF Teleconference 
  Details & Agenda - Tuesday,21 Jan 2003

  

  
Hi 
  Tony,

  
 

  
here 
  you are with a few thoughts on Nikolai's issue.

  
 

  

  
Nikolai is right that 
  <group> and <trans-unit> element have got a lot of common 
  attributes - in fact all possible attributes from <group> are 
  included in the list of attributes for <trans-unit>. In spite of 
  this I'm not sure this would be the 
  best solution to merge those two elements into one as Nikolai suggested. We could just use the 
  elements a little different way. Now I do not have any exact idea 
  and I'm just thinking aloud so anyone 
  feel free to tear it apart. I would add an attribute to the 
  <trans-unit> - similar as 
  Nikolai suggested - called 
  e.g. for-group and we could remove all the attributes from the group 
  element as those are already included in the <trans-unit> 
  element. One <trans-unit> element would contain information for the 
  whole group and the other elements could be nested inside the subgroup. The structure of the file could look 
  like the following:

  

  
 

  
Example 
(simplified)

  
 

  
...

  
<group>         

  
    <trans-unit id="DIALOG1" for-group="yes" font="MS Sans Serif;8" 
  style="WS_POPUP | WS_CAPTION | WS_THICKFRAME" 
  coord="0;0;96;28">

  
        <source/>

  
        <target phase-name="after_resizing" 
  coord="0;0;96;28">    -- local version of dialog 
  coordinates

  
        
  </target>

  
    </trans-unit>

  
    <group>

  
        <trans-unit id="IDC_EDIT1" 
  coord="35;7;53;14">

  
            
  <source/>

  
            
  <target phase-name="after_resizing" 
  coord="40;7;60;14">    -- local version of editbox 
  coordinates

  
            
  </target>

  
        </trans-unit>

  
        <trans-unit id="IDCSTATIC" 
  coord="13;9;23;8">

  
            
  <source>Label:</source> 
  
            
  <target phase-name="after_resizing" 
  coord="25;9;35;8">         -- local version 
  of label coordinates

  
            Translated 
  Label:           

  
            
  </target>

  
         
  </trans-unit>

  
    </group>

  
</group>

  
 

  
 

  
This could solve Nikolai's issue however it 
  could also introduce any new issues I'm not aware of at the 
  moment.

  
I'm looking forward to your 
  response.

  
 

  
Cheers,

  
Mirek

  
    
-----Original Message-----
From: Tony Jewtushenko 
    [mailto:]
Sent: Friday, January 17, 
    2003 7:20 PM
To: 
Subject: 
    [xliff] XLIFF Teleconference Details & Agenda - Tuesday,21 Jan 
    2003

    

    
Dial-in Instructions:
When: 
    Tues,  21 Jan 2003, 04:00PM 
    London/Dublin  / 08:00 AM PST

    

    
UK National 
    Dial-In:      0870 550 3090
International 
    Dial-In:   +44 118 924 0290
Meeting ID: 30543

    
Agenda: 
1/Roll Call  (5 
    min)

    
2/Previous Meeting Minutes - accept as is or 
    amend:  http://lists.oasis-open.org/archives/xliff/200301/msg00014.html

    
3/Reminder regarding OASIS TC 
    Membership policy  - TC membership is terminated after 3 
    consecutive absences,  in some cases 
    without advanced warning.

    
4/Review all remaining Open Issues listed 
    in the tracking report:  http://lists.oasis-open.org/archives/xliff/200301/msg00017.html

    
5/Schedule of remaining work (10 
    minutes)

    
      
21 Jan:     Reformat proposal, Matt (Issue 6)
    
                  Defaults proposal 
      - any additional attributes?, John  (issue 3)
Allow one more meeting to conclude these 
      discussion= 28 Jan
Release Candidate on Jan. 29. 
Allow two meetings 
      discussion of spec changes.
Feb 11 target date

    
Revisions or amendments to the 
    schedule?

    
5/ Carried over from last week:  
    Discussion and response to recent xliff-comment regarding resizing of RC 
    type data within XLIFF - http://lists.oasis-open.org/archives/xliff-comment/200212/msg00000.html .  This query relates to Mat's "reformat" issue 
    (issue # 6)

    
6/Any New Business

    
7/Next meeting - Tues,  28 Jan 2003, 
    04:00PM Europe/London/Dublin  / 08:00 AM PST

    
 

    
 

    
 

    
Tony 
    Jewtushenko                   
    mailto:
Sr. 
    Tools Program Manager   direct tel: +353.1.8039080
Product 
    Management - Tools Technology Team
Oracle Corporation, 
    Ireland