<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
					 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
					 xmlns="http://purl.org/rss/1.0/"
					 xmlns:dc="http://purl.org/dc/elements/1.1/"
					>
<channel rdf:about="http://jasperforge.org/projects/JasperReports/tracker"><title><![CDATA[Latest issues]]></title>
<link>http://jasperforge.org/projects/JasperReports/tracker</link>
<description><![CDATA[Forge latest issues]]></description>
<items>
<rdf:Seq>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4798"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4796"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4795"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4794"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4793"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4791"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4787"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4786"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4785"/>
<rdf:li resource="http://jasperforge.org/plugins/mantis/view.php?id=4782"/>
</rdf:Seq>
</items>
</channel>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4798">
<title><![CDATA[Calls to getName() on conditional styles always return null.]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4798</link>
<dc:date>2010-07-27</dc:date>
<description><![CDATA[Calls to getName() on conditional styles always return null. 

The JRBaseConditionalStyle implementation does not set the 'name' attribute in its constructor.    This makes it impossible to uniquely identify a conditional style in order to apply dynamic formatting programatically.]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4796">
<title><![CDATA[page break element causes infinite loop on file virtualizing]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4796</link>
<dc:date>2010-07-26</dc:date>
<description><![CDATA[using 3.7.1, we have some template that uses the page break element

we are using the file virtualizers and the report gets into an infinite loops that keeps writing to disk forever

swap virtualizer file keeps growing forever, and file virtualizer keeps creating 1K files for ever (even though the report has two pages only)

of course, it all ends up with the disk full and the server down :-)

we see this when exporting to excel and setting pagination off by setting the exporter parameter on the exporter]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4795">
<title><![CDATA[Problem to exporter ODS]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4795</link>
<dc:date>2010-07-26</dc:date>
<description><![CDATA[Encontrado um problema na classe JROdsExporter, ao exporta um relatório de formato ods (Planilha OpenOffice), o mesmo é exportado com  problemas como a falta de textos nas células das planilhas. Nenhuma exceção ocorre na classe sendo somente a exportação do arquivo sem os textos somente com as células da planilha formatadas.

Segue o arquivo exportado em anexo para maior esclarecimento do bug.]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4794">
<title><![CDATA[Possibility to display XML attributes]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4794</link>
<dc:date>2010-07-26</dc:date>
<description><![CDATA[Hello,

It would be nice if we could access the attributes of an xml tag to display.
I have such an issue on amounts where we would like to show the currency. In stead of hard coding this value we added an xml attribute for this purpose. 
On the web,.. it's no problem to read this tag bu I can't seem to find a possibility to do this in the report.

Rgeards,]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4793">
<title><![CDATA[adaptative font sizes]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4793</link>
<dc:date>2010-07-23</dc:date>
<description><![CDATA[would be nice if we could tell to a TextField to start with a Font Size, lets say: 12,  and if the text on it become too much extensive, the Font Size starts to decrease trying to fit the text in the Field area. (size=11, check if fit, if not, size=10, and so on)
Perhaps a property of Minimum Acceptable Size would be needed to not let the text go unreadable.]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4791">
<title><![CDATA[ToolTips not being displayed in PDF and XLS format outputs.]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4791</link>
<dc:date>2010-07-22</dc:date>
<description><![CDATA[When i give an URL to a particular field , I need the tool tip configured to appear on the output formats PDF and XLS generated.]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4787">
<title><![CDATA[Resource Bundle fNot being passed to subreport]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4787</link>
<dc:date>2010-07-20</dc:date>
<description><![CDATA[Hello,

it looks like I might found an issue with the use of Resource Bundle in combination with xpath reports. I already made some reports using a Resource Bundle in combination with SQL. This was working fine. Main and subreport were picking up the needed labels from the Resource Bundle.

When creating a xpath report I always received a Resource Bundle not found for locale error message even though the default Resource Bundle File was available. When searching a bit I found out that it was the subreport Resource Bundle which the report did not manage to find. (Which is strange as it was/is the same file as the main report)

Note: Our resource bundle implementation consists of a piece of Java code which is searching the correct *.properties file itself and passing it as a parameter to the main report (REPORT_RESOURCE_BUNDLE)
It's a bit of a bypass of the functionality where the Resource Bundle files need to be located within the classpath. We pick the file at generation time and pass them trough the report. This gives us a bit more flexibility.

This way of working was working like a charm with SQL reports (some reports have even 3 levels of subreports) and still the resource bundle passed to the main report was being used by the subreports.


]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4786">
<title><![CDATA[Font extension does not support Type 1 fonts]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4786</link>
<dc:date>2010-07-19</dc:date>
<description><![CDATA[Currently, Jasper Reports has Font extension which allows to embed PDF fonts in to the report.  Currently, this font extension supports only True Type Fonts  (ttf fonts) only.  However, it would be great to support Type1 fonts so that it becomes easy while working with Unix/Linux systems.]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4785">
<title><![CDATA[Crosstab filling doesn't scale]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4785</link>
<dc:date>2010-07-19</dc:date>
<description><![CDATA[Please follow to link with the erro description and file attachments:

http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=76778]]></description>
</item>
<item rdf:about="http://jasperforge.org/plugins/mantis/view.php?id=4782">
<title><![CDATA[Copy Text Measurer From JasperServer to JasperReports]]></title>
<link>http://jasperforge.org/plugins/mantis/view.php?id=4782</link>
<dc:date>2010-07-16</dc:date>
<description><![CDATA[On JasperServer there is a "net.sf.jasperreports.text.measurer.factory" called "com.jaspersoft.jasperserver.api.engine.jasperreports.util.SingleLineTextMeasurerFactory" available as an option.

This does not exist under JasperReports. Please add it there.
]]></description>
</item>
</rdf:RDF>