I think it can be solved at all. What ever the OS of the container is,
each client might have a different OS with line endings. Because of
this, I gues that all browser are able to handle "any" line endings
properly. If that is true, than it is only a question of which OS we
use for building the re
And to add to that, I don't think the different line endings rendering
can be solved. When I build the release on laptop, Mac and Linux users
will have different line endings when rendering.
There is only one solution to this: everybody build their own release
directly from CVS, and does this for
Should we replace "\n" in the code with
System.getProperty("line.separator") or is there any xml/html std we
have follow?
Juergen
On 11/4/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Anyhow, now I'm confused. Should I make the next (1.1.x) release with
> my Mac or with my laptop? Doing it on
Anyhow, now I'm confused. Should I make the next (1.1.x) release with
my Mac or with my laptop? Doing it on my mac gives you consistent
results comparing with 1.1. Doing it on my laptop gives you PC line
endings.
Martijn
On 11/3/05, jan_bar <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I compared results
I don't know... It could be that because the 1.1 build was done on my Mac, and the RC builds were done on my MS laptop.
Can you file a bug report, with a more precise description on what you think is wrong?
MartijnOn 11/3/05, jan_bar <[EMAIL PROTECTED]> wrote:
Hi,I compared results of rendered pa
Hi,
I compared results of rendered page from Wicket 1.1-rc2 and final 1.1. In
one page the 1.1 version mixes unix and "microsoft" line endings (it worked
well with 1.1-rc). Is this know bug?
Jan
---
SF.Net email is sponsored by:
Tame your d
