Hi!

Mhh.. the code is not accessible, sorry...
But my eclipse uses UTF-8, the compiler is configured to use UTF-8...
Is there any other way, to check when the String is converted wrong ?!
(I think you're right, its before doxia)

If there is no other solution, i think the string should be defined in
a prop-file...

thanks,

2009/9/3 Hervé BOUTEMY <[email protected]>:
> Hi,
>
> If you're writing your report, ie java code using Doxia API, you're writing
> Strings, without any encoding notion.
> Are you sure the content isn't broken before you send it to Doxia?
>
> Is your code accessible somewhere?
>
> Regards,
>
> Hervé
>
> Le jeudi 03 septembre 2009, [email protected] a écrit :
>> Hello!
>>
>> I'm writing my own maven-report plugin, which should create some output.
>> This output is made with doxia, how it's explained in the tutorials.
>>
>> The problems are the german umlauts. I use it directly in the code (as
>> String) to put via doxia into the html-page.(report)
>> But the report don't shows the umlauts correctly. My problem is, that
>> i don't know, where the encoding for doxia can be changed. (because
>> doxia is initialized within the AbstractMavenReport)
>>
>> I'm a little bit confused, because there are a lot of descriptions in
>> the net, that the default encoding is UTF-8 , so that there should be
>> no problem with german umlauts.
>> I have also tried to use the <project.reporting.outputEncoding>
>> property in the pom, but nothing changes.
>>
>> Are there any experiences with that problem?
>>
>> thanks,,,
>>
>> Dave
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to