[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] String length constraints in 2.0
Hi, Anyone can propose a feature that is not in the wiki simply adding it to section 2. Once the new feature is in the wiki with a good description and a proposed implementation, you can request a ballot for approving the feature. If approved, it will be moved to section 1. After the feature is approved, the owner prepares a draft in any format and sends it to this mailing list. I will add the required changes to the schema and specification. Key points: 1) If none adds the feature in the wiki, it can’t be voted and approved 2) If none prepares a draft for the specification, it will not be added Regards, Rodolfo -- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Jung Nicholas Ryoo +1. Hi All, While looking at the current draft, the feature tracker wiki and the 1.2 specification I noticed that string length constraints or hints are missing for Xliff 2.0. It would probably be good if we added this to the technical items to discuss on an upcoming TC call. In my opinion this would probably best be done as an extension module. I also think there is room for improvement over the 1.2 feature set. I think it might make more sense to have a “maxlength” attribute and an optional specification of what the unit is, instead of “maxbytes”. I also think it could be useful to specify an equivalent size for inline codes that get added to the text size. Regards, Fredrik Estreen -- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]