FW: [xliff] Representing .NET Winforms in Xliff

Here is the promised update

 

Cheers,

-G廨ard

Families are living sanctuaries

 

From: Gerard Cattin
des Bois 

Sent: Tuesday, March 09, 2004 5:26
PM

To: 'Enda McDonnell'

Subject: RE: [xliff] Representing
.NET Winforms in Xliff

 

Hello Enda,

Here is some feedback review on the document.

 

Thanks for taking the time to start it.

 

Font: 

1. move font instruction to
<trans-unit> element. Ok

Embedded menus: 

1.ok to delimit menus with semicolons. 

2. Menus in their own group and referenced
via menu attribute of dialog group: does it mean each menu in a different
group?

Other embedded items

1. Does it mean storing binary resource
data in skeleton?

Tooltips

1. We use \\ to introduce tool tips.

2. ok to use <trans-unit> in dialog
<group> with restype = tooltip

Inheritance

1. How do you propose to specify in an
attribute that a control is inherited?

Optimization

1. We need to support the scenario where
full satellite assemblies are produced, not just fallbacks. 

Baml

1. xaml does not provide key value pairs. 

2. Wondering how every one is going to get
their flattened tree…

 

Cheers,

-G廨ard

Families are living sanctuaries

 

From: Enda McDonnell
[mailto:] 

Sent: Tuesday, February 17, 2004
3:41 AM

To: 

Subject: [xliff] Representing .NET
Winforms in Xliff

 

Hi guys,

 

Here are the initial findings by Gerard Cattin des Bois and
myself on using the current Xliff Winres Profile for Dialogs to
represent .NET Winforms.

 

Regards,

Enda McDonnell

 

 

 

 

  
  
Alchemy Software Development Ltd. 

  Block 2 Harcourt Business Centre
    

    Harcourt Street 

Dublin 2 

Ireland
  

  
Tel : (353)-1-708 2800 

  Fax : (353)-1-708 2801 

  Web :www.AlchemySoftware.ie