On 03.01.2007 17:47, Ard Schrijvers wrote:
Locally we added this svn 'pre-commit' hook to prohibit a commit that
did not contain a reference to a jira issue. In jira, via an issue,
you can then find the commits that below to it. Although it is
sometimes a little annoying, it forces everybody her
>
> On 1/3/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
>
> > ...Not sure wether it is common practice to create a jira
> issue for it when committing
> > something new and resolve it?...
>
> I don't think it's common practice here but IMHO it's a Good Thing.
Locally we added this svn 'pre-c
On 1/3/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
...Not sure wether it is common practice to create a jira issue for it when
committing
something new and resolve it?...
I don't think it's common practice here but IMHO it's a Good Thing.
-Bertrand
>
>
> Ard Schrijvers skrev:
> > Sry for the delay.
> >
> > Shall I commit the StripNameSpaceTransformer to
> trunk/core/cocoon-pipeline/cocoon-pipeline-components/./tr
> ansformation , or is there a more preferable location? Should
> I also add it to the branch?
> >
> Seem like a reason
Ard Schrijvers skrev:
Sry for the delay.
Shall I commit the StripNameSpaceTransformer to
trunk/core/cocoon-pipeline/cocoon-pipeline-components/./transformation , or
is there a more preferable location? Should I also add it to the branch?
Seem like a reasonable place as long as the cocoo
On 1/3/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
Should I also add it to the branch?
+1
-Bertrand
Sry for the delay.
Shall I commit the StripNameSpaceTransformer to
trunk/core/cocoon-pipeline/cocoon-pipeline-components/./transformation , or
is there a more preferable location? Should I also add it to the branch?
Ard
> >
> > > 1) The lightweight StripNameSpaceTransformer ... Add
> > >
>
> > 1) The lightweight StripNameSpaceTransformer ... Add
> > this to trunk/branch or not?
If no objections, I'll add my version of the StripNameSpaceTransformer to the
trunk/branch on short notice
>
> +1
>
> > 2) The XHTML serializer: Make it by default strip the list of
> > namespaces we
On 07.12.2006 11:51, Ard Schrijvers wrote:
1) The lightweight StripNameSpaceTransformer ... Add
this to trunk/branch or not?
+1
2) The XHTML serializer: Make it by default strip the list of
namespaces we know people don't want to sent to the browser.
-1 No, please don't. If you have a brow
On Dec 7, 2006, at 2:51 AM, Ard Schrijvers wrote:
1) The lightweight StripNameSpaceTransformer is an option to strip
intermediate namespaces you want to get rid of (like after sql
transformer, I would like to get rid of them as fast as possible). Add
this to trunk/branch or not?
+1
2) The
Recapitulating this thread:
1) The lightweight StripNameSpaceTransformer is an option to strip intermediate
namespaces you want to get rid of (like after sql transformer, I would like to
get rid of them as fast as possible). Add this to trunk/branch or not?
2) The XHTML serializer: Make it by d
Piotr,
It could be a problem with the mime-type.If you're using
'application/xhtml+xml' IE6 will not handle it correctly. I'm not sure
about IE7 though.
Reijn
falcorn wrote:
I'm using IE7.
But this is much complicated problem, i think.
When I use this xsl stylesheet to remowe attributes wit
I'm using IE7.
But this is much complicated problem, i think.
When I use this xsl stylesheet to remowe attributes with namespace prefixes,
it works.
when I use map:read instead of map:generate it works too(with xmlns:i18x
attribute).
Maybe it is problem with serialization? (Does IE work with xhtml
Sorry Piotr,
which version of IE are you using? I can see pages containing xmlns
declarations with all IE versions I have here in my office.
Quite commonly the "blank page in IE" is caused by a head like this :
IE is intelligent enought to think that the full page is a title. This
h
Ard Schrijvers wrote:
...I replaced this xsl transformer with a custom
StripNameSpacesTransformer
(about just 10 lines), which outperforms the slow xsl
transformation a factor 30...
This would be useful to have in Cocoon, go for it!
I thought it was too trivial :-)
There is also less tri
On Dec 5, 2006, at 9:29 AM, Simone Gianni wrote:
Yep, the problem with this approach is that you manage to know if a
namespace declaration has been used only when you reach the end of the
document (after checking that no element used it)
Yeah, it takes two passes. Better to declare up-front
Mark Lundquist wrote:
>
> Is there ever a need to retain namespace declarations for namespaces
> that are not actually used in the result document, i.e. for which
> there is no element with that namespace? I think the idea is to just
> delete extraneous namespace declarations, not to delete them a
On 12/5/06, Mark Lundquist <[EMAIL PROTECTED]> wrote:
On Dec 5, 2006, at 8:38 AM, Simone Gianni wrote:
> Care is required : some emerging internet standards (XForms for
> example,
> but also others) do require namespaces, so :
> - Okay for the HTML serializer
> - Not okay for the Xhtml serializ
On Dec 5, 2006, at 8:38 AM, Simone Gianni wrote:
Care is required : some emerging internet standards (XForms for
example,
but also others) do require namespaces, so :
- Okay for the HTML serializer
- Not okay for the Xhtml serializer, in this case eventually provide a
list of namespaces to rem
On 12/5/06, Simone Gianni <[EMAIL PROTECTED]> wrote:
Peter Hunsberger wrote:
> Instead of requiring that an extra transformer be added to the
> pipeline would it make sense to add this capability as a configuration
> option on the HTML/XHTML serializers?
>
Care is required : some emerging interne
Peter Hunsberger wrote:
> Instead of requiring that an extra transformer be added to the
> pipeline would it make sense to add this capability as a configuration
> option on the HTML/XHTML serializers?
>
Care is required : some emerging internet standards (XForms for example,
but also others) do re
On Dec 5, 2006, at 7:35 AM, Peter Hunsberger wrote:
Instead of requiring that an extra transformer be added to the
pipeline would it make sense to add this capability as a configuration
option on the HTML/XHTML serializers?
+1
IIRC this very thing was proposed some time ago and either reject
On 12/5/06, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
> You should add an extra stylesheet that removes superfluous namespace
> attributes. This is what I've done:
I used to use this strategy as well, though recently I replaced this xsl
transformer with a custom StripNameSpacesTransformer (ab
Ard Schrijvers said the following on 5/12/06 12:40:
...I replaced this xsl transformer with a custom
StripNameSpacesTransformer
(about just 10 lines), which outperforms the slow xsl
transformation a factor 30...
This would be useful to have in Cocoon, go for it!
I thought it was too trivial
>
> > ...I replaced this xsl transformer with a custom
> StripNameSpacesTransformer
> > (about just 10 lines), which outperforms the slow xsl
> transformation a factor 30...
>
> This would be useful to have in Cocoon, go for it!
I thought it was too trivial :-)
Will add it to trunk/branch
On 12/5/06, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
...I replaced this xsl transformer with a custom StripNameSpacesTransformer
(about just 10 lines), which outperforms the slow xsl transformation a factor
30...
This would be useful to have in Cocoon, go for it!
-Bertrand
Ard Schrijvers wrote:
You should add an extra stylesheet that removes superfluous namespace
attributes. This is what I've done:
I used to use this strategy as well, though recently I replaced this xsl transformer with a custom StripNameSpacesTransformer (about just 10 lines), which outperform
> You should add an extra stylesheet that removes superfluous namespace
> attributes. This is what I've done:
I used to use this strategy as well, though recently I replaced this xsl
transformer with a custom StripNameSpacesTransformer (about just 10 lines),
which outperforms the slow xsl tra
falcorn said the following on 4/12/06 13:47:
I removed dtd declaration and xml:space attribute has gone;
But there is declaration of xmlns:i18n at html tag.
And IE dosen't like this attribute. I get blank page.
In FF everything is correct, I only get some warrnings from Tidy that there
is not st
I removed dtd declaration and xml:space attribute has gone;
But there is declaration of xmlns:i18n at html tag.
And IE dosen't like this attribute. I get blank page.
In FF everything is correct, I only get some warrnings from Tidy that there
is not standard attribute at html tag: xmlns:i18n
greet
What exactly do you mean with this page is not visible in MSWord. What
happens if you open the page in your browser?
Sorry. It is my fault.
Now it is correct.
I was thinking about IExplorer.
Greetings
--
View this message in context:
http://www.nabble.com/i18nTransformer-problems-with-static
There are strange xml:space tag.
And in MsWord this page is not visible.
What exactly do you mean with this page is not visible in MSWord. What
happens if you open the page in your browser?
What i've done wrong?
Could You help me?
Greetings Piotr
Reijn
Piotr,
this also happens when using Xalan. It seems that by removing the dtd
declaration the xml:space tags are removed.
Kind regards,
Jeroen Reijn
falcorn wrote:
I've commented this i18n transform tag. And is the same.
So it isn't i18nTransformer problem.
But where is a problem?
Can it be
I've commented this i18n transform tag. And is the same.
So it isn't i18nTransformer problem.
But where is a problem?
Can it be because i'm using saxon as default xslt transformer?
--
View this message in context:
http://www.nabble.com/i18nTransformer-problems-with-static-pages-tf2750404.html#a
Hi Piotr,
are you sure it comes from the i18n transformer? What happens if you comment
out the i18n transformer and look at the result of the pipeline?
Kind regards,
Jeroen Reijn
Hippo
-Original Message-
From: falcorn [mailto:[EMAIL PROTECTED]
Posted At: Monday, December 04, 2006 11:44
35 matches
Mail list logo
