I have been doing dynamic PDF creation via ASP.net for some time -- in the form of HTML to PDF conversion. It works well for us, but we have accessibility requirements from the State to make everything is accessible. For static PDFs, we simply "tag" the files manually using Adobe's accessibility tools. Of course this does not work for dynamically created files. PDFs that I create dynamically fail the Acrobat Pro Accessibility test.
Does anyone have any ideas about create PDFs dynamically in ASP.net, but producing PDFs that are tagged and can pass the Adobe Accessiblity test? I have researched many components, but none that I have found support tagging.
Thanks.
I would look seriously at iText. AFAIK, this is the definitive library for creating dynamic PDF's, for Java and .NET.
You will need the book iText in Action.
Here's a quote from iText in Action on accessibility:
"You can use iText to create a document that passes all the criteria that are listed in Section 508."
Related
I am new to Adobe cq5. Went through many online blogs and tutorials but could not get much. Can any one describe a way how I can create an HTML page from Adobe Illustrator (.ai) file containing images and font, required for web page.
I have installed CQ5 instance on my system but don't know how to work with AI files.
Thanks in advance.
Simply put you can't. For starters CQ5 is a modular CMS in that you drag in various components to build a page up. You have page templates that contain the basics of a page such as the header and footer but you don't create entire pages in one go so to speak. You build them up from reusable components.
Second you can't automatically convert an illustrator file to a webpage, you need a web developer to translate it into HTML, Javascript, JSP's and CSS. Also CQ5 can require quite a bit of back end coding in Java so that is something to keep in mind.
CQ5 is really an enterprise CMS so depending on your needs it might be worth taking a look at something like Wordpress although you still wont be able to simply upload an AI file.
You can use Adobe Illustrator (.ai) to build graphics for use within an AEM web site. You place those graphics in the the AEM DAM (Digial Asset Manager). You can then use those assets. For example:
1 - reference them in web pages.
2 - build components that use them. See http://scottsdigitalcommunity.blogspot.ca/2013/04/creating-gallery-components-that.html
As a new user, I recommend that you read this: http://helpx.adobe.com/experience-manager/using/onboardAEM.html.
From that link - you will find a section about creating your first AEM site. Its a must to walk through to learn AEM.
You will also find other articles that will show you how to perform tasks - like creating OSGi services.
I just began working with ASP.NET and I'm trying to bring with me some coding standards I find healthy. Among such standards there is the multilingual support and the use of resources for easily handling future changes.
Back when I used to code desktop applications, every text had to be translated, so it was a common practice to have the language files for every languages I would want to offer to the customers. In those files I would map every single text, from button labels to error messages. In ASP.NET, with the help of Visual Studio, I have the resort of using the IDE to generate such Resource Files (from Tools -> Generate Local Resource), but then I would have to fill my webpages with labels - at least that is what I've learned from articles and tutorials. However, such approach looks a bit odd and I'm tempted to guess it doesn't smell that good as well. Now to the question:
Should I keep every single text in my website as labels and manage its contents in the resource files? It looks/feels odd especially when considering a text with several paragraphs.
Whenever I add/remove something, e.g.: a button, to an aspx file I would have to add it to the resource file as well, because generating the resource file again would simply override all my previous changes to it. That doesn't feel like a reusable code at all for me.
Perhaps I got it all wrong from tutorials as it doesn't seem like a standardized matter - specially if it required recompiling the entire application whenever some change has to be done.
Best practices for ASP.NET Web Forms localization have not really changed much over the years. If you don't have much dynamic content then you can get away with implicit localization and bind web forms controls (form elements and yes, even labels) to resource files. Explicit localization is useful if you want a bit more control over where localized text is rendered in a control with multiple captions or something you've created yourself. You don't need to look very far for instructional steps from MS on how to do either of these.
Walkthrough: Using Resources for Localization with ASP.NET
If your localization requirements are more dynamic, for example, you want to easily provision new languages, centralize resources, or you need to provision new string captions on a new dimension (like per client), then you need to get a bit more creative. .NET allows you to extend the
the resource provider and you can implement a database backend that allows for easy administration of localized resources.
Extending the ASP.NET 2.0 Resource-Provider Model, Building a Database Resource Provider
Extending Resource-Provider for storing resources in the database * A more recent implementation
Or you could just roll your own!
I've also dug up a duplicate SO post. It's a few years old, but speaking from experience I believe the advice found on the referenced code project page are still true (for Web Forms): Globalization and localization demystified in ASP.NET 2.0
I hope that helps! If you have any more specific questions regarding localization please add them to your Questions or comments.
I am looking for easy solution to convert documents from one format(doc, html, xls...) to pdf in ASP.NET.
Is the iTextSharp a good choise? Can iTextSharp convert documents from one format to pdf?
What library can your suggest me to use?
I've been using winnovative for all my PDF generation for the past few years:
http://www.winnovative-software.com/
Fair few good features, and simple to implement, if you don't mind paying for a license.
The default standard for this task should be Microsoft Office SharePoint Server. Another option would be using Microsoft Office applications from ASP.NET with Automation, combined with a PDF Printer (you will need a copy of Microsoft Office installed on the server). There are many PDF printers outthere (Cute PDF for example), but if you can afford a commercial option I recommend Amyuni PDF Converter. There are samples of Word/Excel to PDF conversion using Office+Automation with this product.
I'm working as Developer Evangelist with Aspose. And I would like to share with you that you may try Aspose.Total for .NET product suite, which allows you to convert various file formats (DOC/DOCX/PPT/PPTX/XSL/HTML etc.) into PDF format. You may also select components of your choice. Complete samples, tutorials and support are also available for these components.
Please note that these components are standard .NET assemblies and you can use them either in ASP.NET or Windows Forms applications.
Give the Muhimbi PDF Converter Services a look. It installs in your environment as a scalable and robust Windows Service and has specifically been designed for use from server based applications such as ASP.NET.
It comes with a friendly web services based interface that allows it to be used from most modern environments such as Java and .NET. It supports all common as well as some not so common file formats. Watermarking and PDF Security is included as well. If you have SharePoint in your environment then a SharePoint optimised version is available as well.
Disclaimer, I have worked on this product so the usual disclaimers apply. Having said that, it works great.
I have an asp.net site which is essentially a repository of documents uploaded by users.
I would like visitors to the site to be able to view any of these documents in some sort of "document viewer" without ever being able to download the file to their local system.
Documents are all Office files and PDFs.
Please advise if there are open source or commercial "document viewer" controls that you have used and would recommend.
EDIT: I own the server and can load any server components. Unfortunately i can't use flash based viewers as it must be compatible accross all browsers and devices.
We had a similar requirement and we converted all office docs and PDF files to SWF files using Print2Flash (http://print2flash.com/) and display them in the browser. There are both free and commercial editions of print2flash.
Just answering for anyone else looking up this info.
I ended up going with Adeptol's Ajax Document Viewer which works really well.
I need a component that I can install on my server that can be used in an ASP.NET Web Application to:
Display word documents, PDF documents, images in the browser.
Allow these documents to be annotated online and have those annotation saved for redisplay later.
Thanks in advance.
Only a technology like Flash or Silverlight would be able to approach providing that functionality. The biggest benefits would be avoid cross-browser/platform issues and decent security.
Also, I would be guessing that if Flash/Silverlight components are available to do this, they would not be cheap due to the licensing of Adobe and Microsoft document formats etc.
Standard .NET custom/user controls are simply not an option as they generate HTML based user interfaces.
Sorry I don't have any more specific suggestions.