On Wed, May 5, 2010 at 4:05 PM, Marcos Caceres marc...@opera.com wrote:
On Wed, May 5, 2010 at 3:59 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
On 5 May 2010, at 10:40, Robin Berjon wrote:
On May 4, 2010, at 19:29 , Scott Wilson wrote:
I've just been reading through the WARP spec
!
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On Tue, May 11, 2010 at 3:55 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
Hi Marcos,
I'll make a start on tests for the assertions about correctly processing the
element (6-13).
I'm not sure about assertion 5, however - how would you tell if it had been
processed
On May 11, 2010, at 9:00 PM, Scott Wilson scott.bradley.wil...@gmail.com
wrote:
On 11 May 2010, at 15:58, Marcos Caceres wrote:
On Tue, May 11, 2010 at 3:55 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
Hi Marcos,
I'll make a start on tests for the assertions about correctly
-
hence CORS/UMP applies and WARP can be ignored. In cases where the
origin is unknown, then WARP applies.
[1] http://dev.w3.org/2006/waf/widgets-land/#introduction
[2] http://dev.w3.org/2006/waf/widgets-access/
HTH!
Marcos
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http
Hi,
Can we please rename the View Mode Media Feature to The 'view-mode'
media feature? The current name of the spec is confusing [me].
Kind regards,
Marcos
--
Marcos Caceres
Opera Software
to widgets, so we took widgets
out of the name.
--
Marcos Caceres
Opera Software
On 5/19/10 1:42 PM, Robin Berjon wrote:
On May 18, 2010, at 10:45 , Marcos Caceres wrote:
Can we please rename the View Mode Media Feature to The 'view-mode' media
feature? The current name of the spec is confusing [me].
Ooh, a naming discussion!
I only brought it up because it's your
/Chromium take up this opportunity to work with us.
Kind regards,
Marcos
[3] http://www.w3.org/2008/webapps/wiki/WidgetImplementation
[4] http://www.wholesaleappcommunity.com/Develop/WIDGETS/Forms/AllItems.aspx
[5] http://incubator.apache.org/wookie/
[6] http://www.w3.org/TR/test-methodology/
[7
On Tue, May 25, 2010 at 10:27 AM, Aaron Boodman a...@google.com wrote:
On Tue, May 25, 2010 at 1:19 AM, Marcos Caceres marc...@opera.com wrote:
W3C's widget specs are mature (i.e., most at CR or LC) and the working
group believes them to be technically sound and, with a few
extensions, able
reinforced.
Fixed.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
[http://dev.w3.org/2006/waf/widgets/#example-of-usage5]
Comment:
The Chinese characters in name xml:lang=zh-cn?/name have become
corrupted.
fixed.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
/widgetsgt;
lt;name short=Weathergt;
Weather! a totally awesome application!
lt;/namegt;
lt;name short=آب و هوا xml:lang=fa dir=rtlgt;
lt;span dir=ltr xml:lang=engt;Weather!lt;/spangt; برنامه واقعا بزرگ
lt;/namegt;
lt;/widgetgt;
Fixed
--
Marcos Caceres
Opera Software ASA, http
the spec.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
would
prefer the term localizable string, localizable, or language string.
Changed to localizable string globally... though Ishida string
would have been my preference :)
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
, it doesn't in fact even
require UAs to support all the view modes. I'd expect that an application
running on an iPhone would only support maximized and fullscreen — if it
applied different style rules for each, it would still be 100% conformant.
FWIW, I agree with Robin here.
--
Marcos
break implementations of the Widgets Packaging spec)?
Kind regards,
Marcos
[1] http://tools.ietf.org/html/draft-abarth-mime-sniff-05
--
Marcos Caceres
Opera Software
anything else to help with the
process.
On Thu, Jun 17, 2010 at 8:22 AM, Marcos Caceres marc...@opera.com
wrote:
Hi Adam,
I'm writing on behalf of the Web Apps WG to inquire as to the
status of the
Media Type Sniffing spec [1]. The Widgets Packaging specification
is ready
to proceed
and non-linguistic or undetermined or at least default
content (which is what you mean). Note that the tag und represents text
whose language cannot be determined. I would suggest default content here
(and elsewhere).
Fixed. Used default content globally.
--
Marcos Caceres
Opera
:
Please note that, while case has no meaning in language tags, it is
recommend that with xml:lang authors use the case conventions
recommended in BCP 47.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
a List of Keywords From an Attribute no longer
returns a localized string (as directionality does not apply to this
kind of attribute).
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
tags in lowercase form as the names of folders.
Thanks again, Addison, for all your time and help!
--
Marcos Caceres
Opera Software
be tightly controlled.
Is that the direction you're suggesting? Marcos, what do you think?
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
Hi Ricardo,
(moving discussion to public-webapps)
On 7/2/10 5:56 AM, Ricardo Varela wrote:
hallo all, hallo Marcos,
We have a small question regarding what we interpret may be an
inconsistency in the behaviours for parsing a config file as commented
in the W3C widget packaging spec [1
the
implementation report and test-suite.
Kind regards,
Marcos
--
Marcos Caceres
Opera Software
Ok, please let me know if you need me to clarify anything in the spec.
I'm happy to help where I can. Please also note that I checked in a
bunch of tests relating to viewmodes today.
Kind regards,
Marcos
On 7/7/10 6:39 PM, Ricardo Varela wrote:
hallo Marcos (and sorry for the confusion
test suite is
about 1 week out from being uploaded!
More details coming soon.
Kind regards,
Marcos
--
Marcos Caceres
Opera Software
On 8/5/10 3:30 PM, Web Applications Working Group Issue Tracker wrote:
ACTION-568: Create an alternative mechanism for openURL and send it to the mail
list (Web Applications Working Group)
http://www.w3.org/2008/webapps/track/actions/568
On: Marcos Caceres
Due: 2010-08-12
If you do
On 8/10/10 9:03 AM, gaut...@opera.com wrote:
Quoting SULLIVAN, BRYAN L (ATTCINW) bs3...@att.com:
Marcos,
You're saying if I understand you, that if I create an anchor:
a href=http://mywidget.com;Click to load the online version/a
That when the user clicks this link it will launch
On 8/16/10 8:30 PM, Web Applications Working Group Issue Tracker wrote:
ACTION-570: Update packaging-configuration.rnc to reflect the iew-modes in the
CR (Web Applications Working Group)
http://www.w3.org/2008/webapps/track/actions/570
On: Marcos Caceres
Due: 2010-08-23
Fixed
that the Overview document is just a copy/paste from another test suite,
so contains errors... just scroll to the bottom of the page and click on
Product ua to access the tests):
http://dev.w3.org/2006/waf/widgets-vmmf/test-suite/
Comments welcomed...
Kind regards,
Marcos
--
Marcos Caceres
Opera
Update: based on feedback, we have rewritten the tests. The tests no
longer assume a default view mode, and no longer use any javascript.
Again, please review and send feedback.
On Sat, Aug 21, 2010 at 7:36 PM, Marcos Caceres marc...@opera.com wrote:
Hi,
Opera has completed the first draft
recently corrupted. (They won't unzip using standard zip desktop tools
either)
Re-uploaded all the tests, and we fixed the borked tests too. Happy
testing :)
S
On 3 Sep 2010, at 19:55, Marcos Caceres wrote:
Hi,
Please be warned that following tests have some bugs. We will fix them
next week
:
pspan style=unicode-bidi: bidi-override; direction:ltr
קחללפם/span/p
Should work fine in all browsers.
On 5 Sep 2010, at 23:24, Marcos Caceres wrote:
On 9/4/10 4:54 PM, Scott Wilson wrote:
I'm also getting a Zip file error on the i18n-039 040 sets
(these are the only ones I've implemented so
went loopy! :( I'm on it!
On 6 Sep 2010, at 12:54, Marcos Caceres wrote:
On 9/6/10 12:25 PM, Scott Wilson wrote:
To be honest I've been having problems with the i18n test cases
generally. For example:
Tests that LRO direction applies to the name element. To pass,
the displayed value must
Ok, I think I fixed it... maybe.. hopefully :)
On 9/6/10 3:05 PM, Marcos Caceres wrote:
On 9/6/10 3:03 PM, Scott Wilson wrote:
Something else went strange with the tests - they have odd new names
and url's that don't work:
E.g.
Test b5 has been renamed to:
http://dev.w3.org/2006/waf
3 years with Widgets. We really appreciate
all your time, help, and patience. Personally, I can wait to see
developers making use of these features.
Kind regards,
Marcos
On 8/5/10 3:10 PM, Web Applications Working Group Issue Tracker wrote:
ACTION-567: Notify the I18N Core WG about the I18N
and runtimes? All and any comments
are welcomed!:)
Please send feedback to public-webapps public-webapps@w3.org
Kind regards,
Marcos
[1] http://dev.w3.org/2006/waf/widgets-digsig/
--
Marcos Caceres
Opera Software
On Wed, Sep 8, 2010 at 12:34 PM, Marcos Caceres marc...@opera.com wrote:
Opera would like to announce the first release of the test suite for the
Digital Signatures for Widgets specification [1]. The test suite is here:
http://dev.w3.org/2006/waf/widgets-digsig/test-suite/
The WebApps WG
already implemented in the main
context?
Best,
Nathan
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On 9/16/10 6:10 PM, Nathan wrote:
Marcos Caceres wrote:
On Thu, Sep 16, 2010 at 1:42 PM, Nathan nat...@webr3.org wrote:
cc: public-webapps
Hi Claes,
Nilsson, Claes1 wrote:
Hi Nathan,
Thanks for clarifying your proposal.
I interpret you so that you are proposing standardization
On 9/16/10 6:17 PM, Nathan wrote:
Marcos Caceres wrote:
On Fri, Sep 3, 2010 at 7:52 PM, Nathan nat...@webr3.org wrote:
Hi All,
Simply wondering why WARP, Widgets Updates and Digital Signatures aren't
used to deploy js applications which run in the main browser context?
I guess because
Hi Nathan,
On 9/16/10 7:38 PM, Nathan wrote:
Marcos Caceres wrote:
On 9/16/10 6:10 PM, Nathan wrote:
Marcos Caceres wrote:
As above. I thought that was what we (Web Apps WG - Widgets) have been
doing for the last 5 years?
Maybe I've missed part of the specifications - are you telling me
of true for required
instead.
Fixed the value of config.xml name, as it was wrong. Changed test
pass condition so required does not need checking.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
, Art Barstow
[CR] http://www.w3.org/TR/2010/CR-view-mode-20100624/
[Widget] http://www.w3.org/TR/widgets/#abstract
--
Marcos Caceres
Opera Software
On 9/30/10 9:35 PM, Web Applications Working Group Issue Tracker wrote:
ACTION-587: PC spec: license element doesn't define its Expected Children (Web
Applications Working Group)
http://www.w3.org/2008/webapps/track/actions/587
On: Marcos Caceres
Due: 2010-10-07
If you do not want
the resource
at
'http://dev.w3.org/2006/waf/widgets-api/test-suite/test-cases/ta-bb/aq/pass.html'
and continue executing the script as normal.
/test
--
Marcos Caceres
Opera Software
(wrong link to test in prev email, correct link below...)
On Sat, Oct 2, 2010 at 3:58 PM, Marcos Caceres marc...@opera.com wrote:
The Widgets test suite has been updated. We have removed tests for openURL,
as it was dropped from the Widget Interface spec.
For 9 assertions there are now 50
note in PC about this?
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
[2] http://www.w3.org/TR/2010/WD-api-perms-20101005/
Best,
Mike
--
Michael Hanson, Mozilla Labs
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
, by making sure the user agent treats as
malformed XML. To pass, the user agent must treat this as an invalid
widget.
http://dev.w3.org/2006/waf/widgets/test-suite/test-cases/ta-klLDaEgJeU/005/amp.wgt
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
XML. To pass, the user agent must treat this as an invalid widget.
[0] http://www.w3.org/2008/webapps/track/issues/150
[1] http://www.w3.org/2008/webapps/track/issues/151
[2] http://www.w3.org/2008/webapps/track/issues/152
--
Marcos Caceres
Opera Software
on the icon elements or any of its attributes.
What effect specifying a global attribute has on an elements is
determined by Step 7 of this specification.
Does that help?
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On Thu, Oct 14, 2010 at 5:58 PM, Phillips, Addison addi...@lab126.com wrote:
Hello Art, Marcos, and Webapps,
During our teleconference yesterday [1], I was tasked with formally replying
to this request on behalf of the Internationalization WG.
I would still like to see the 'locale' field
On Tue, Nov 2, 2010 at 9:36 AM, viji v...@borqs.com wrote:
Hello Marcos
The changes for Email attribute and Rule for Getting Text Content with
Normalized White Space seem fine.
Good to hear!
I have a comment on usage of Global attributes for Icon, Feature, Content
and Param elements
.
I've changed to ...using technologies such as...
--
Marcos Caceres
Opera Software
the word SED change
to DES, to be in sync with the example The Awesome Super bdo
dir=rtlDude/bdoWidget in pc spec. Does it expect the character to
be changed from lt to gt.
Same behavior applies to i18n-ltr 010 020, i18n-rlo 020 etc
I had a look, I think the tests are correct.
--
Marcos Caceres
The following tests were wrong, so I removed them from the VMMF test
suite. They were wrong because the UA is free to choose the most
suitable viewmode, and is under no obligation to respect the author's
wishes for a particular view mode.
test for=ta-vmmf id=ordered
The default value column of the Table of Configuration Defaults
doesn't map, nor should it map, to the underlying implementation of user
agent (i.e., it does not map to C or Java, as there is no notion of a
null in some languages and these specs are not implemented in
JavaScript). Hence I
I've removed the following test case. It will be properly testing in the
widget API spec.
test id=ds for=ta-xGYcVTMoAX
src=test-cases/ta-xGYcVTMoAX/000/ds.wgt
Tests that the user agent correctly sets the configuration defaults.
To pass,
author email must be null,
I've removed the following tests from the test suite as they don't make
sense. The reason is that a UA ignores the value of width and height for
raster graphics, so thus making the following untestable at runtime.
test for=ta-nYAcofihvj id=i18nlro24
src=test-cases/i18n-lro/024/i18nlro24.wgt
Removed the following test case as it's too much of an edge case:
test id=hh for=ta-ZjcdAxFMSx
src=test-cases/ta-ZjcdAxFMSx/002/hh.wgt
Test the UA's ability to correctly find config document. To pass, the
user agent must correctly load pass.html from config.xml and treat
CONFIG.xml as an
had
limited interest.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
to the X509Data node.
I've updated the tools on the W3C site to automatically add all the
certificates needed to new signatures created with
./create-test-case.sh, so this should be a problem no more.
Stuart
Kind regards,
Marcos
, and locales/en/icon.jpg (ordering of the
items in the list is irrelevant).
The actual icons included are icons/pass.png and locales/en/icon.png
(not .jpg).
Fixed. Committed.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
it.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On Fri, Dec 3, 2010 at 12:19 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
See:
http://dev.w3.org/2006/waf/widgets/test-suite/test-cases/i18n-lro/001/i18nlro01.wgt
This is pretty obviously not what should be in here!
S
Fixed.
--
Marcos Caceres
Opera Software ASA, http
is:
feature name=feature:x-bugus-feature required=false dir=rtl/
So as the feature is unsupported by the UA, the feature is ignored and the
value of the required attribute is irrelevant. (All other xxx30 tests have
the same issue).
Can you suggest an alternative way to test this?
--
Marcos
On 12/3/10 5:38 PM, Scott Wilson wrote:
On 3 Dec 2010, at 16:28, Marcos Caceres wrote:
On Fri, Dec 3, 2010 at 12:05 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
# i18nlro30 (download, files)
Tests that LRO direction does not apply to the feature element's required
attribute
be lt; PASSED --gt;/description
/widget
I'm ok with those changes. Please also update the hook.js files :)
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On Fri, Apr 30, 2010 at 5:16 PM, Marcos Caceres marc...@opera.com wrote:
Hi Richard,
On Fri, Mar 26, 2010 at 9:32 PM, Richard Ishida ish...@w3.org wrote:
The example looks rather baroque, but I think it does illustrate a number
of points. (I think that in real life it may be simpler to just
in (if such information was declared via xml:lang in the
widget's configuration document).
Kind regards,
Marcos
On 1/5/11 1:47 PM, Charles McCathieNevile wrote:
On Wed, 05 Jan 2011 12:39:05 +0100, Marcos Caceres marc...@opera.com
wrote:
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface
On 1/10/11 3:39 PM, Robin Berjon wrote:
On Jan 10, 2011, at 15:33 , Marcos Caceres wrote:
On 1/10/11 2:27 PM, Arthur Barstow wrote:
Hi Marcos - have you checked with the I18N Core WG? My recollection is
this functionality was added to the Widgets API spec based on their LC
comments.
I'll
On 1/10/11 4:28 PM, Robin Berjon wrote:
On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
I would be happier if we could break up the Widget PC spec into:
* Packaging (zip only requirements) * XML Configuration for
widgets * XML Localization and Folder-based Localization
I could live
On 1/17/11 1:56 PM, Robin Berjon wrote:
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
On 1/10/11 4:28 PM, Robin Berjon wrote:
I would argue that it's not particularly complicated to implement,
and we are seeing it used in Opera extensions: we have extensions
in 15 languages as of today
On 1/21/11 11:48 AM, Robin Berjon wrote:
On Jan 19, 2011, at 19:39 , Marcos Caceres wrote:
On 1/17/11 1:56 PM, Robin Berjon wrote:
Nothing in P+C is super-hard to implement, but the l12n parts
account for most of the complexity,
I've only implemented the i18n stuff in Javascript, but I
widgets and other
technologies? Did I miss the memo?
Kind regards,
Marcos
On Tue, Jan 18, 2011 at 2:03 PM, Philippe Le Hegaret p...@w3.org wrote:
Dear Web Application Working Group,
Today W3C introduced an HTML5 logo for public consideration:
http://www.w3.org/News/2011#entry-8992
The W3C
On 1/23/11 6:31 PM, Charles Pritchard wrote:
Ian has, for quite some tine, described his whatwg document as HTML
Next, a 'living' standard.
Yes, we did the same with W3C Widgets. We dropped versioning and
(unsuccessfully) requested the W3C to change its process to allow the
latest version to
to updating the spec,
changing the test cases, and republishing as a new LC ASAP.
Kind regards,
Marcos
On Wed, Jan 26, 2011 at 2:42 PM, Marcos Caceres marc...@opera.com wrote:
Dear Web Apps WG,
Opera would like to provide some feedback based on our implementation
experience of the Widgets Digsig specification.
Generally, we found that the specification is implementable but have
significant
On Wed, Jan 26, 2011 at 5:35 PM, Marcos Caceres marc...@opera.com wrote:
On Wed, Jan 26, 2011 at 2:42 PM, Marcos Caceres marc...@opera.com wrote:
Dear Web Apps WG,
Opera would like to provide some feedback based on our implementation
experience of the Widgets Digsig specification.
Generally
On 1/31/11 7:52 PM, Arthur Barstow wrote:
Andrey - on January 26, Marcos proposed changing the c14n algorithm in
[1] and [2] and notified the group in [3] that he updated the Editor's
Draft [ED] to reflect his proposal. He included rationale in [1].
Marcos - in what way(s) does your proposal
On 1/31/11 8:18 PM, Marcos Caceres wrote:
On 1/31/11 7:52 PM, Arthur Barstow wrote:
Andrey - on January 26, Marcos proposed changing the c14n algorithm in
[1] and [2] and notified the group in [3] that he updated the Editor's
Draft [ED] to reflect his proposal. He included rationale in [1
On 2/1/11 1:41 PM, Arthur Barstow wrote:
Hi Marcos,
On Jan/31/2011 2:18 PM, ext Marcos Caceres wrote:
On 1/31/11 7:52 PM, Arthur Barstow wrote:
Andrey - on January 26, Marcos proposed changing the c14n algorithm in
[1] and [2] and notified the group in [3] that he updated the Editor's
Metereológico
/name
/widget
As there was confusion with regards to the email attribute and the param
elements name and value attributes being defined as keyword attributes,
these have now been reclassified as a string attributes.
]]
Kind regards,
Marcos
On 2/3/11 8:08 PM, Arthur Barstow wrote:
On Feb/1/2011 1:30 PM, ext Marcos Caceres wrote:
I have updated the Wigets PC spec for publication as a LC.
This new draft specifies the defaultlocale attribute
Is support for this proposed attribute going to be added to the Widget
object? (I don't
xmlns = http://www.w3.org/ns/widgets;
version = 2.0
type=eol
details
A serious security issue was found in this widget.
It is highly recommended you uninstall it.
/details
/update-info
--
Marcos Caceres
Opera Software
concerns are you having or what interop issues do you foresee?
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http://datadriven.com.au
On 2/7/11 4:43 PM, Scott Wilson wrote:
On 7 Feb 2011, at 14:22, Marcos Caceres wrote:
On Mon, Feb 7, 2011 at 1:46 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
I really like the Kill Switch/EOL idea and having a type
attribute to specify it, but I'm concerned that the Patch type
Hi Tim,
In [1], it sounds to me like you are after W3C Widgets [2]; we have
almost finished standardizing them so no need to wait.
You can play with them today in Opera [3] and a bunch of other great
runtimes [4].
Kind regards,
Marcos
[1] http://lists.w3.org/Archives/Public/www-tag/2011Feb
, written in the (ASN.1) form, but in this
test I see only some byte array without any ASN.1 tags.
May be the signature value is packed somehow? Haw can I unpack it?
Regards,
Andrey
On 1/31/2011 9:52 PM, Arthur Barstow wrote:
Andrey - on January 26, Marcos proposed changing the c14n algorithm
Hi.
Its been 3 month and we still dont have a reply? Should we seek establishing
official test suites our selves outside the w3c?
On 16 Nov 2010 11:46, Anne van Kesteren ann...@opera.com wrote:
Marcos Caceres from Opera started a wiki on Testing Requirements some time
ago. I just updated
Hi Dom, or W3C Staff,
Can we please get a full rundown of the systems available on test
server. Can we also have all the details about getting access to the
server, etc.
Kind regards,
Marcos
On Tue, Feb 15, 2011 at 10:44 AM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 15 Feb 2011 10:42
On Wed, Mar 16, 2011 at 5:35 AM, Phillips, Addison addi...@lab126.com wrote:
Hi,
One more minor note. In the grammar in section 5.3, you have:
low-alpha = %x61-71
I suspect you mean for this to be:
low-alpha = %x61-7a
Fixed.
--
Marcos Caceres
Opera Software ASA, http
(or not) and what is
meant by case sensitive if it is supported (just ASCII case? Unicode
default case mapping?)
Search for case-sensitively or case-sensitive instead. The
case-sensitive requirement on files comes a fair bit.
--
Marcos Caceres
Opera Software ASA, http://www.opera.com/
http
On 3/17/11 1:43 PM, Robin Berjon wrote:
On Mar 17, 2011, at 20:21 , Marcos Caceres wrote:
On Tue, Mar 15, 2011 at 4:41 PM, Phillips, Addisonaddi...@lab126.com wrote:
I happened to be referring to the Widget spec this morning
Out of curiosity: in what context?
1. Section 5.3 (Zip Relative
On 3/17/11 1:14 PM, Arthur Barstow wrote:
[Ooops; Sent before read ... ]
Marcos - Addison's comments were submitted during the comment period of
a proposal to publish a new LCWD of this spec. I think that publication
should be blocked until there is consensus on how to address the comments.
I
Hi Art,
On 3/17/11 1:14 PM, Arthur Barstow wrote:
[Ooops; Sent before read ... ]
Marcos - Addison's comments were submitted during the comment period of
a proposal to publish a new LCWD of this spec. I think that publication
should be blocked until there is consensus on how to address
701 - 800 of 1132 matches
Mail list logo
