Jump to content
We've recently updated our Privacy Statement, available here ×

lucianc

Members
  • Posts

    5,609
  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Security Advisories

Downloads

Everything posted by lucianc

  1. Explaining how Arabic fonts work is a vast subject. I don't think this forum has the breadth to host it. If you're interested in the subject, you can look for resources on the GSUB and GPOS tables of OpenType fonts (e.g. http://partners.adobe.com/public/developer/opentype/index_table_formats1.html, http://partners.adobe.com/public/developer/opentype/index_table_formats2.html, https://fontforge.github.io/gposgsub.html, etc). Note thought that iText (which JasperReports uses to created PDFs) does not make use of the OpenType tables. It implements its own ligature processing in ArabicLigaturizer. iText is open source, so you can take a look and see how it works (it basically uses hardcoded ligatures). Also note that in other contexts JasperReports uses the standard java.text.Bidi class to determine the directionality of a text (as defined by the Unicode standard). If you have an Arabic text that doesn't display properly in a report, I suggest attaching a self contained test case to reproduce the problem.
  2. PDF files as produced by JasperReports (via iText) are binary files and need to be directly written to binary/byte streams. It cannot not be interpreted as character data in any charset/encoding. Regards, Lucian
  3. You can do that by passing a value back and forth via a subreport parameter and a return value. See an example in the attached files. Regards, Lucian
  4. There is no direct way of feeding two values per record into a single series in HTML5 charts. You can contact the Jaspersoft commercial support and file a feature request (or bug if you consider it so). Depending on your exact use case, there might be some workarounds. For instance, if you only need to feed two values (that is a single record) into the chart, you can create a subdataset and pass a data source with two records to it. That is something like: <subDataset name="ChartDataset"> <field name="key"/> <field name="value" class="java.lang.Integer"/> </subDataset> <hc:chart xmlns:hc="http://jaspersoft.com/highcharts" xsi:schemaLocation="http://jaspersoft.com/highcharts http://jaspersoft.com/schema/highcharts.xsd" type="Pie">...<multiAxisData><multiAxisDataset> <dataset> <datasetRun subDataset="ChartDataset"> <dataSourceExpression>new net.sf.jasperreports.engine.data.JRMapCollectionDataSource([[key: "a", value: 5], [key: "b", value: 10]])</dataSourceExpression> </datasetRun> </dataset> </multiAxisDataset> <dataAxis axis="Rows"> <axisLevel name="Key"> <labelExpression><![CDATA["Key"]]></labelExpression> <axisLevelBucket class="java.lang.String"> <bucketExpression><![CDATA[$F{key}]]></bucketExpression> </axisLevelBucket> </axisLevel> </dataAxis> <multiAxisMeasure name="Measure" class="java.lang.Integer" calculation="Nothing"> <labelExpression><![CDATA["Measure"]]></labelExpression> <valueExpression><![CDATA[$F{value}]]></valueExpression> </multiAxisMeasure> </multiAxisData> Note that the example uses Groovy expressions for the sake of list and map literals. If you need to feed several records into a single chart, something similar can be achieved by collecting the value into a list. That would be more tedious though. Regards,Lucian Chirita
  5. See http://community.jaspersoft.com/wiki/fake-title-and-summary-sections and http://community.jaspersoft.com/wiki/how-can-i-suppress-page-headers-and-footers-when-exporting-xls Regards, Lucian
  6. Do you want to change the labels printed on the category/X axis, or the labels printed on bars (which are shown when the isShowLabels flag is set)? The label expression is used for the labels printed on bars (I'm assuming it's a bar chart). If you want to change the X axis labels you need to add the text to the category expression. Regards, Lucian
  7. The label expression in pie datasets is required to evaluate to Strings, and there is no automatic conversion from other types. If you want an integer to display as label, you can use $V{value}.toString() or TEXT($V{value}, "#,###.00") if you want a specific format. Regards, Lucian
  8. You can authenticate with anonsvn/anonsvn. Regards, Lucian
  9. The JasperReports Server Web Services Guide includes a section named "Logout" that contains details about how to close sessions. Doing that would release the memory used by a report as soon as the report/session is no longer needed. Regards, Lucian
  10. The fix is included in JasperReports 6.1.1.
  11. lucianc

    Expressions

    Changed Resolution from Open to Fixed Changed Status from New to Resolved File the style problem as a separate issue.Closing this as the dataset parameter issue should be fixed.
  12. Can we see the JRXMLs involved in this? It would be easier to tell what happens if we'd see the actual reports. Regards, Lucian
  13. I updated the XSD files on http://jasperreports.sourceforge.net/xsd with the schema files that correspond to the latest release (6.1.0). We'll consider qualifying the XSD files with release names. That's not strictly required because we keep the schema backward compatible, so as long as we have the latest schema on sourceforge.net it would validate JRXML files produced by any JR version. But having separate schemas per versions might play a role in the compatibility mode in JSS. We'll have to think whether it would help there.
  14. Could you please detail the "xml file will complain about non existent attributes". Where exactly does that happen? When JasperReports loads an JRXML file, it uses an internal XSD file and not the public http://jasperreports.sourceforge.net/xsd/jasperreport.xsd Regards, Lucian
  15. Changed Resolution from Open to Reopened Changed Status from Assigned to Resolved Support for Hibernate 4.0 has been added at http://sourceforge.net/p/jasperreports/code/ci/3e6f6266f075e5775ef87971f13e3ab1eddc38be/Regards,Lucian
  16. Changed Assigned User from @User_306070 to - Please include details on how the image is loaded as a java.awt.Image object, and the JRXML of the report where the image is displayed. We need a complete test case to understand what's happening.Regards,Lucian
  17. Changed Resolution from Open to Fixed Changed Status from Assigned to Resolved Fixed at http://sourceforge.net/p/jasperreports/code/ci/3e6f6266f075e5775ef87971f13e3ab1eddc38be/The JR HQL query executer now works with Hibernate 3.6 and continues to work with older versions as well.Regards,Lucian
  18. Changed Resolution from Reopened to Works as Designed Changed Status from Feedback Requested to Resolved As explained above, styled texts parse their value expression as XML. If one wants a field value to be preserved as is inside a styled text (as opposed to being parsed/interpreted as XML), the value needs to be explicitly encoded for XML (using JRStringUtil.xmlEncode($F{..}) for instance).Regards,Lucian
  19. Changed Resolution from Open to Fixed Changed Status from Assigned to Resolved Implemented in 6.1 by allowing HTTP (remote) locations for all file based data adapters (including JSON). Jaspersoft Studio can be used to create such data adapters.Regards,Lucian
  20. Changed Resolution from Open to Fixed Changed Status from Acknowledged to Resolved Implemented as dataset run return values in 5.1.2.Regards,Lucian
  21. Additional commit at http://sourceforge.net/p/jasperreports/code/ci/013e03ad98b5ccaad75a3c96eefa6d26e7c93b10 to fix a problem introduced by the previous change.
  22. See http://jasperreports.sourceforge.net/api/net/sf/jasperreports/engine/design/JRDesignTextElement.html#setHorizontalTextAlign%28net.sf.jasperreports.engine.type.HorizontalTextAlignEnum%29 Regards, Lucian
  23. Changed Resolution from Open to Fixed Changed Status from New to Resolved Changed Assigned User from @User_306070 to @lucianc Fixed at http://sourceforge.net/p/jasperreports/code/ci/f40318f6fbedefbb5ab7e10e66592ae75e7d5a9e by initializing JRBaseFiller.pageWidth before the group bands get created. At some point we should consider refactoring the filler initialization process to make it more robust.Thank you for investigating this,Lucian
  24. Changed Resolution from Open to Fixed Changed Status from Confirmed to Resolved Fixed at http://sourceforge.net/p/jasperreports/code/ci/0314182153cc8cd72c0955bdbffc2b7317015e95/Thank you for the investigation, I can't tell how this managed to slip through.Regards,Lucian
×
×
  • Create New...