[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: WG: failure notice]
| Subject: | WG: failure notice |
|---|---|
| Date: | Fri, 19 Sep 2003 18:39:31 +0200 |
| From: | "Florian Sachse" <fsachse@pass-engineering.com> |
| To: | <Tony.Jewtushenko@oracle.com> |
Dear Tony, I'm not able to post my emails to xliff-comment@lists.oasis-open.org. Can you please help? Best regards, Florian -----Ursprüngliche Nachricht----- Von: MAILER-DAEMON@mail.oasis-open.org [mailto:MAILER-DAEMON@mail.oasis-open.org] Gesendet: Freitag, 19. September 2003 18:22 An: fsachse@pass-engineering.com Betreff: failure notice Hi. This is the qmail-send program at mail.oasis-open.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.: Sorry, only subscribers may post. If you are a subscriber, please forward this message to xliff-comment-owner@lists.oasis-open.org to get your new address included (#5.7.2) --- Below this line is a copy of the message. Return-Path: Received: (qmail 13961 invoked by uid 60881); 19 Sep 2003 16:22:16 -0000 Received: from fsachse@pass-engineering.com by hermes by uid 0 with qmail-scanner-1.15 (spamassassin: 2.55. Clear:SA:0(0.0/7.0):. Processed in 0.281252 secs); 19 Sep 2003 16:22:16 -0000 Received: from unknown (HELO pass-engineering.com) (212.63.133.106) by mail.oasis-open.org with SMTP; 19 Sep 2003 16:22:15 -0000 Received: from PCFLORIAN [62.134.108.51] by pass-engineering.com with ESMTP (SMTPD32-7.13) id AD721D450090; Fri, 19 Sep 2003 18:23:14 +0200 From: "Florian Sachse" To: Subject: Dialog Representation in "XLIFF Profile for Windows Resources" Date: Fri, 19 Sep 2003 18:22:34 +0200 Message-ID: <002e01c37eca$3c4a4620$332aa8c0@PASS> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=0.0 required=7.0 tests=none version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Dear TC, I'm not happy with XLIFF representation for dialogs (3.6.1. Dialog Box-Level Data). I assume that you already have discussed this issue in detail and came up with this soultion, but still let me give my comments;-) My question is where to place dialog attributes coord, font, style which are likely to be changed. The changed values will have to be written to the target of the first trans-unit. When processing an XLIFF file we normally can work with this rule: To get target information look for a target element and use the contents. For all attributes which could be of interest, check if the target has them, if not look up one level (trans-unit) and use those values. According to the document this will not work for a dialog because in this case the attributes are stored in the group and not in the first trans-unit. Even if the definition looks natural (coord belong to the dialog-group), it in fact makes processing more complicated. For a dialog which normally contains a caption we already need a special trans-unit to keep the caption text. But this one has also to be handled differently from other trans-unit in terms of where to look up attributes. Storing the dialog attributes in the first trans-unit gets together all localizable information in much the same way as it is done in all other cases. We just need to keep in mind that the first trans-unit contains information about the dialog. This is a style issue but it also has practical impact: The need to look up attributes from a higher group-level than a trans-unit means more checks and processing time because groups can be defined for other reasons at any level and the nearest parent group must not be the right one. It is also not good to simply look up the request parent in the chain of parents to take the first one. This might cause problems for other resource formats. These formats are not defined yet, but why not use a scheme that will work fine for other resource formats, too. So my proposal is: For a dialog put all the attributes but restype and resname from the group to the first trans-unit. Best regards from Bonn, Florian Florian Sachse Managing Director PASS Engineering GmbH Remigiusstr. 1 53111 Bonn Germany phone: +49-228-697242 fax: +49-228-697104 email: fsachse@pass-engineering.com web: www.passolo.com egroup: www.egroups.com/group/passolo Florian Sachse Managing Director PASS Engineering GmbH Remigiusstr. 1 53111 Bonn Germany phone: +49-228-697242 fax: +49-228-697104 email: fsachse@pass-engineering.com web: www.passolo.com egroup: www.egroups.com/group/passolo
-- Tony Jewtushenko mailto:tony.jewtushenko@oracle.com Principal Product Manager direct tel: +353.1.8039080 ST Tools Technology Team Oracle Corporation, Ireland
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]