Accessible Tagged PDF with BIRT - eclipse

We are using BIRT to create PDF-files from our website, but now we need to change the PDFs to meet the accessibility demands. I have tried to search for an answer how to make accessible tagged PDF with BIRT, but haven't found any answer. Even this https://www.eclipse.org/birt/ documentation doesn't talk about accessibility nor making tagged PDF.
So is it possible to add tags with BIRT or do we need to change BIRT to some completely different tool? If we need to change the tool, I would much appreciate info about tool which we could use. We have quite many PDF templates created with BIRT and all need to be changed to meet the accessibility demands.

With the Open Source version of BIRT, creating tagged PDFs is not possible AFAIK.
However, in a BIRT IDE built from source, it looks as if development in this direction started (IIRC there were "PDF Tag" properties in the advanced properties).
Maybe the commercial BIRT version from OpenText can generate tagged PDFs - I don't know and I would really appreciate more info about this topic from the BIRT project.
Edit: According to http://otadocs.opentext.com/documentation/ihub3/help/adg/adg24/index.html#page/ADG/DesigningReport.1.03.html#, this should be possible with the commercial version.

Related

Does Redmine provide any graph report options

Does Redmine tool provide any plugin to generate graphs for the issues?
Like, i need to generate a pie or bar graph for no. of issues raised for current week/month etc. Can someone please help me with this?
There are indeed some Redmine plugins that provide graphical reports. Some of them (more or less) usable also for issues. The free one's are listed on Redmine.org in the plugin directory, the others are commercial plugins.
Like the following one's:
Redmine Reporting Plugin
Plugin for the Redmine issue tracker
Best thing would be:
Make your custom queries
In every of these queries export the csv file
Take it from excel

Jasper Reports Pro library for Compile & Generating HTML5 reports

We have built our own reporting engine where we compile and fill jrxml's using Jasper Reports library.
Recently, we are planning to include HTML5 charts to our reports. Evaluated JasperStudio 6 professional and created a chart which uses highchart.
We need this jrxml containg highchart to be compiled and filled using jasper report library, but couldnt find any documentation where I can download jasperreport-pro jar files.
I installed JasperServer-pro and can see jasperreports-pro-6.0.0.jar in their WEB-INF/lib folder. But where can I download these libraries and use it standalone?
I went through https://community.jaspersoft.com/wiki/jars-required-compile-simple-jrxml-html5-element which explains which jars are needed. But they say 'shipped with pro JasperReports API' which I cannot locate to download and evaluate.
supposing that you are a paying customer, since HTML5 charts are PRO only, I highly suggest you to contact the Technical Support. They will provide you all the info.
Some details must be set, like property for license location and others related to HTML5 configuration.
Regards,
Massimo.
P.S: you could also try to open a ticket on the JasperReports tracker asking them to detail the linked wiki article.

Jasperreports community version doesnt allow interactive reports?

I am using jasperreports-server-5.1.1 , and i am using the REST api to integrate jasperreports with my app.
The api for running reports mentions the parameter "interactive=true", but also mentions - "In a commercial editions of the server where HighCharts are used in the report,
this property determines whether the JavaScript necessary for interaction is
generated when exporting to HTML." .... which i interpret as "only available with commercial edition". Am i right ?
Also, pagination doesnt work.... so is it also allowed only on, commercial edition ?
thanks
As far as I know the ad-hoc reporting component is only available in the Pro version (i.e. commercial edition). The community edition is really just a teaser but not really useful for production environments. Did you have a look at ReportServer? It's completely open source, allows you to execute Jasper Reports (and Eclipse Birt if you want) and comes with powerful ad-hoc reporting capabilities.

Create Task Report from Mylyn?

is there a way to create a task/activity report (say a weekly report) off tasks managed with Mylyn? I've been using Rachota TimeTracker which allows me to create reports (in html format)
http://rachota.sourceforge.net/en/demo.html
I've just started using mylyn (our company uses Embarcadero JBuilder which is is based on Eclipse), but I don't see anywhere in the Eclipse or Embarcadero docs about reporting capabilities.
Is it possible? Is it possible to query activities worked on a prior week and report statistics out of it (management like reports, you know;) I'm sure it is, but I haven't been able to google it out.
Thanks.
You're in luck, Tasktop Pro (the supported version of Mylyn) has reporting. It allows you to:
View all task activity times for the previous day, week, and month
Manually adjust times as necessary to account for meetings and discussions
Submit your adjusted times, on tasks you select, to your task repository
Create reports in various formats
I'd recommend this short video which explains the reporting features in about 6 minutes.
David Shepherd
Tasktop Technologies
As you already know by now, the reporting functionality is included into commercial Tasktop product, which is developed by the same people who created Mylyn. So, obviously they are not interested to include some features into a free version. Now you have two options, either buy Tasktop, or develop your own extension for Mylyn. The task data is stored in reasonable simple xml file, so you not necessarily have to create an Eclipse plugin.
the reporting feature was stripped from the project when it used to be called mylar, in 2007, and since the project went commercial never came back to the open source mylyn for obvious reasons..
I found this simple perl script which outputs a pretty basic text only report, good enough for me.
http://rachaelandtom.info/mylyn-report
No takers? Not surprised since I can't find anything on the subject. For what's worth, there is an experimental task/activity report available for Mylyn with the sandbox jar. However, I could not get mine to work as I'm tied up with a JBuilder installation behind a firewall (and I can't download anything on the corp network that is not pre-evaluated... it sucks, I know.)
I'm going to have to experiment with the mylyn sandox at home, but it would be great if someone knows of an easier, more stable alternative.

What is a good tool for writing a user manual (help file), which integrates with version control [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
The people writing the user manual are not necessarily programmers, and they need a visual editor. A major issue is the internal format of the authoring tool; it should be readable text/html, so it's easy to compare versions of individual pages checked into version control.
DocBook
(source: docbook.org)
Microsoft HTML Help Workshop can be used to create good quality professional CHM help files. All you need is a bunch of HTML files. The tool "compiles" all these and bundles into a single Help file.
The HTML files can be generated using Microsoft Word/Frontpage or even Dreamweaver. You might want to consider source controlling these HTML files.
Latex. Lyx provides WYSIWYM for writing latex files.
At my old job they used a tool by madcap software called flare.
It seemed to work really well.
There are other professional products which allow help file writing and they have support of "context ID" which makes context sensitive help possible. Doc To Help and RoboHelp are these type of products.
A good combination to consider is Subversion, DocBook and Publican.
Version control = Subversion
Content Authoring = DocBook
Publishing = Publican
Optional WYSIWYG = Serna
At the moment, this is one of the toolchains in use by the world's largest provider of open source solutions, and the name behind much of the world's use of Linux-based operation systems in the enterprise market. Most (and close to all) of Red Hat's official documentation is created in such a manner. Same goes for Fedora.
The major "pro" here is that these are freely available tools, with a strong overlap in the market of technical writers. All of which will be able to (but might not want to) write in XML, and picking up DocBook is like picking up HTML in the 90's. Subversion is a very common version control tool, that like DocBook is relatively easy to implement and use. Publican is a great publishing tool that can take DocBook XML, and publish it to PDF, HTML, HTML-single, etc. Obviously your writers can use a WYSIWYG like Serna, but I use snippets in Geany (on Fedora) or TextMate (on OS X) personally.
The major "con" is the perception of technicality. Your writers might want WYSIWYG (and can have it), and depending on your documentation needs, this might be what you end up using. As you would know, there's a market out there for "Technical Writers" who specialize in fixing Microsoft Word styles (and markup), so the arguments for separating "authoring" from "publishing" are based on proven but distinct use cases for organizations that require documentation to be held up to the same standards of the engineering/programming/source production.
Some of the extreme advice you will get comes from people and companies that have been exposed to the value of XML documentation, and especially those in the realms of DITA, where certain multi-nationals have a reputation for acquisitions that are influenced by the format and availability of the product knowledge. there are also the arguments that locking your documentation into a "sticky" or closed format doesn't help the future maintenance requirements. This is where the open source options gain support on a corporate level. Plus, obviously, it's free.
You can use Subversion and MGTEK Help Producer. Help Producer makes help files from Word documents. TortoiseSVN comes with scripts to compare different revisions of Word documents, in Word itself (Word has a version compare tool).
Your users are going to want a visual diff tool that resembles the one they are editing in. If they are just slightly not-technical, DocBook or Latex aren't going to work (I've tried giving my users both, and I even tried Epic Editor as a DocBook editor which is very expensive but didn't work out very well after all). Sticking to something they know (Word) will prevent you many headaches.
I was very reluctant to go this route at first too, because I wanted a solution that was more 'technically perfect', but I realized over time that having happy and productive users was more important. Just saying that I know where you're coming from, but try the Word route - it works much better in practice than all the 'pure' text-based solutions that are out there. Regular users don't like markup based editing.
If you're using Visual Studio, take a look at SandCastle - http://www.codeplex.com/Sandcastle.
There's also a couple of tools that help you build sandcastle files, try searching "sandcastle" on codeplex. One of them is SandCastle Help File Builder (http://www.codeplex.com/SHFB), but I've never used it so I don't know if non-technical users will be happy with that.
Mapcap Flare is the best commercial tool around. Written by the ex-developers of Robodoc
I created a documentation system called Mandown (Markdown/Html/Javascript/file-based relatively linked documents for portability) which would easily go under version control. The visual editor part you would have to figure out separately - I sometimes use HTML-Kit which at least has a preview feature.
See What is the best way to store software documentation?
Here's another tool to check out: Xilize
We are using APT. It integrates well with the CI (standard build artifact) and is more alive than for instance word document. It is also possible to generate PDFs and other formats when needed.