Activity for Docmenta
-
Pascal Patronidis created ticket #73
Individual font for PDF export
-
Hello, I need to integrate a link to an external PDF-Document. I tried several things but no.one is working. E.g. i imported pdf into the folder files, used an alias and tried to make a link in a text. I wanted to open the pdf in an exported html-help but it works not. How can I do it?
-
Carsten Kossendey created ticket #72
Bildertausch und Appearence
-
Frank posted a comment on ticket #71
It seems that it's up again.
-
Sorry for the late answer. I have cleared the browser-cache and also checked the editor. It says tinymce_3_5_11_b In the meantime I had to switch to Windows 10, and actually I can't reproduce it. I will post a new Issue with the HTML-Source if it happens agein.
-
Pfiffikus created ticket #71
project's homepage continuously down
-
Manfred P. modified a comment on ticket #70
I could not reproduce it with Chrome (68.0). In the video it looks like you are pressing the Delete key. Does the problem exist for any text and any key? If problem exists only for specific text, could you please send me the HTML source of the content-node where this problem exists. I have seen that you are using an old TinyMCE version (3.5.8.b). Probably you have installed the TinyMCE 3.5.8.b plugin. Does the problem also exist if you select the latest TincMCE version (3.5.11.c) in the user profile?...
-
I could not reproduce it with Chrome (68.0). In the video it looks like you are pressing the Delete key. Does the problem exist for any text and any key? If problem exists only for specific text, could you please send me the HTML source of the content-node where this problem exists. I have seen that you are using an old TinyMCE version (3.5.8.b). Probably you have installed the TinyMCE plugin. Does the problem also exist if you select the latest TincMCE version (3.5.11.c) in the user profile? You...
-
Chrome looses style settings for text
-
Both issues should be fixed in version 1.9.3 (also the unicode linebreaks have been added to punctuation.props).
-
Fixed in version 1.9.3.
-
Docmenta released /bin/v1-9-3/docmenta_v1-9-3_tomcat7_win64_setup.exe
-
-
-
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
It seems this problem can appear after some network problems. As a result the saved output configuration is invalid and remains invalid. To fix a broken output configuration, please try one of the following two possibilities: 1) Create a completely new output configuration Create a new output configuration with new identifier. Do not(!) use the "Copy" button because this will also copy the invalid setting. Configure the new output configuration with the required settings for odd pages. Optionally...
-
Detlef M. posted a comment on ticket #38
... yes, but you run into trouble when you add content above this manual intervention. This kind of documentation errors is very easy to be overlooked. A real continuation option would be nice.
-
Manual GUI language
-
Language codes more precise
-
For me, manual copying is too risky (to be forgotten). Let me explain, what I am used to (commercial authoring system) and what I feel is a useful approach: All nodes are accessible via a central pool. Each node can be referenced should the author of the new document like it. As soon as a document gets released, all linked nodes get frozen. When viewing a document in its tree view, all linked nodes which are not in their latest version are marked. Therefore the author can check the changes of those...
-
Maybe the term "product" (as it is used in Docmenta) is misleading. The original idea was, that different products should be independent of each other. That means if you change the content in one product, you should be sure that it has no impact on any other product (at least as soon as a product version is released). Furthermore, two different products could be stored at different locations in the filesystem (or one product is stored as plain files and the other is stored in a database). From a...
-
Maybe the term "product" (as it is used in Docmenta) is misleading. The original idea was, that different products should be independent of each other. That means if you change the content in one product, you should be sure that it has no impact on any other product (at least as soon as a product version is released). Furthermore, two different products could be stored at different locations in the filesystem (or one product is stored as plain files and the other is stored in a database). From a...
-
Maybe the term "product" (as it is used in Docmenta) is misleading. The original idea was, that different products should be independent of each other. That means if you change the content in one product, you should be sure that it has no impact on any other product (at least as soon as a product version is released). Furthermore, two different products could be stored at different locations in the filesystem (or one product is stored as plain files and the other is stored in a database). From a...
-
Maybe the term "product" (as it is used in Docmenta) is misleading. The original idea was, that different products should be independent of each other. That means if you change the content in one product, you should be sure that it has no impact on any other product (at least as soon as a product version is released). Furthermore, two different products could be stored at different locations in the filesystem (or one product is stored as plain files and the other is stored in a database). From a...
-
Maybe the term "product" (as it is used in Docmenta) is misleading. The original idea was, that different products should be independent of each other. That means if you change the content in one product, you should be sure that it has no impact on any other product (at least as soon as a product version is released). Furthermore, two different products could be stored at different locations in the filesystem (or one product is stored as plain files and the other is stored in a database). From a...
-
... same request from me! But first some appraisal: I stumbled across Docmenta and had quite some "Wow!"-moments reading the docs. Docmenta contains a lot of thoughtful implementation and intuitive approaches and came close to be the hottest candidate for my future documentation tasks. But then came this show-stopper. Sigh. I definitely need to share nodes across products. In fact I would even like to put all nodes into a central pool and just link them into the products. ... which is the normal...
-
Translation offline?
-
Danny Buddenberg posted a comment on ticket #66
Thank you very much. Fixing the already exported publication worked fine. Next we will try to edit the punctuation.props.
-
I found another issue. It seems that somewhere in your content there is a Unicode line-break U+2028 (probably in content node with alias "Zeitklassen") . This unicode line-break is not recognized by the indexer as whitespace. This causes a Javascript error in the generated index file (index-3.js). This can be fixed as follows: In your Docmenta installation, open the file apache-tomcat/webapps/docmenta/docbook-xsl/webhelp/template/content/search/punctuation.props in a text-editor and add the following...
-
I found another issue. It seems that somewhere in your content there is a Unicode line-break U+2028 (probably in content node with alias "Zeitklassen") . This unicode line-break is not recognized by the indexer as whitespace. This causes a Javascript error in the generated index file (index-3.js). This can be fixed as follows: In your Docmenta installation, open the file apache-tomcat/webapps/docmenta/docbook-xsl/webhelp/template/content/search/punctuation.props in a text-editor and add the following...
-
I found another issue. It seems that somewhere in your content there is a Unicode line-break U+2028. This unicode line-break is not recognized by the indexer as whitespace. This causes a Javascript error in the generated index file (index-3.js). This can be fixed as follows: In your Docmenta installation, open the file apache-tomcat/webapps/docmenta/docbook-xsl/webhelp/template/content/search/punctuation.props in a text-editor and add the following line at the end: Punct29=\u2028 Then export the...
-
I found another issue. It seems that somewhere in your content there is a Unicode line-break U+2028 (HTML entity ). This unicode line-break is not recognized by the indexer as whitespace. This causes a Javascript error in the generated index file (index-3.js). This can be fixed as follows: In your Docmenta installation, open the file apache-tomcat/webapps/docmenta/docbook-xsl/webhelp/template/content/search/punctuation.props in a text-editor and add the following line at the end: Punct29=\u2028 Then...
-
Yes. That workaround solves the "cropping". "Rangreihe" remains "rangreihe". But unfortunately docmenta still can not find the searchterm. Although the word certainly occurs in the WebHelp.
-
Yes. That workaround solves the "cropping". "Reihereihe" remains "rangreihe". But unfortunately docmenta still can not find the searchterm. Although the word certainly occurs in the WebHelp.
-
This is a bug that affects German and French output language. The WebHelp fulltext search includes so called "stemmer" for the English, French and German language. The stemmer shall reduce words, which have the same meaning, but only differ in the suffix, to the same "base-word". Unfortunately, in the generated HTML output always the English stemmer file is referenced, even if the output language is German or French. This will be fixed in the next Docmenta version. Until then, as a workaround, you...
-
This is a bug that affects German and French language. The WebHelp fulltext search includes so called "stemmer" for the English, French and German language. The stemmer shall reduce words, which have the same meaning, but only differ in the suffix, to the same "base-word". Unfortunately, in the generated HTML output always the English stemmer file is referenced, even if the output language is German or French. This will be fixed in the next Docmenta version. Until then, as a workaround, you can fix...
-
Yes, the export language ist German. In our case the search found nothing - neither "Rangreihe" nor "Rangreih". Many search terms get cropped, but not every term. "Zeitklassen" got "zeitklass", "Tabellierung" got "tabellier" and "Vorfilter" got "vorfilt". So it's not always cut above 8 letters. Many other terms don't have a problem at all: "Medienanalyse", "Grundgesamtheit" and "Planeingabe" are doing well. You can access the documentation at http://docs.comsulting.net/topmodular/prod/content/ch...
-
In case the export language is German, I found following issue: "Rangreihe" is not found, but "Rangreih" is found. For export language "English" this problem does not appear. I will further have to investigate on that problem. Though I cannot completely reproduce the situation in your screenshot, where search term is cropped in the result panel.
-
In case the export language is German, I found following issue: "Rangreihe" is not found, but "Rangreih" is found. For export language "English" this problem does not appear. I will further have to investigate on that problem. Though I cannot completely reproduce the situation in your screenshot, where search term is cropped in the result panel
-
Hello, this will be fixed with the next version. Sorry for the inconvenience caused!
-
To find the invalid nodes, please run a consistency check on the document root. Normally this message should only appear if the XHTML source is not well-formed.
-
Please attach the HTML source of the content nodes (the including and the included content). Thanks!
-
Webhelp Search crops the search term
-
Davyd REY created ticket #65
org.docma.util.XMLParseException: Closing tag 'td' has no matching opening tag!
-
FATAL Error during export to PDF (and docbook)
-
PDF export: Includes werden nicht über den Seitenumbruch fortgeführt
-
PDF Export: Includes at the end of a page are not shown completly
-
An out-of-the-box import functionality does not exist. Though, such functionality could be implemented through the plug-in API.
-
revive online published export after upgrade
-
Gábor Abramov posted a comment on ticket #58
Thanks, my problem has been solved.
-
CHM files and WebHelp importing ...
-
Update: Support of video tag has been added in Docmenta version 1.9.2.
-
-
-
-
-
-
Since Docmenta version 1.8 this can be set in the application settings. Set the path to the fop-config.xml in the field "Custom FOP configuration File" (see http://www.docmenta.org/onlinedocs/content/app_settings.html).
-
The TinyMCE 4 differs a lot from the TinyMCE 3. Actually I already tried to upgrade to TinyMCE 4, but unfortunately a lot of functionality that was available in version 3 is no longer available in version 4. Currently I'm working on integration of CKEditor editor into Docmenta. It should be available in few months.
-
Hello, I think the problem is, that the assigned font used for PDF output does not have the glyphs for all Hungarian characters. Please try following: use a text-editor to create a text-file with following code: <?xml version="1.0" encoding="utf-8" ?> <fop> <renderers> <renderer mime="application/pdf"> <fonts> <auto-detect/> </fonts> </renderer> </renderers> </fop> Name the file, for example, fop_config.xml and place it somewhere in your filesystem, for example in the document-store directory of...
-
As a solution export the document as a single HTML and print it as PDF.
-
Editor upgarde
-
PDF output Hungarian character coding problem
-
Currently the video tag is not directly supported by Docmenta. It will be supported in the next release of Docmenta. However there are workarounds for using the video tag in Docmenta. Currently the video tag does not work in WebHelp V2 output, because the video tag is not recognized as a file link. Therefore, the file is not exported. That means, in the exported publication the video does not work, because the referenced file-path file/FILE_ALIAS does not exist. As a workaround, I'd recommend that...
-
Kristaps Kietis created ticket #57
Tag video is dropped, when I create export.
-
-
I cannot reproduce the issue ... what a pity :( try if problem also exists with some other browser yes, it persists for iron 61.0.3200.0 e.g. which browser are you using? Firefox 56.0
-
-
-
-
-
I cannot reproduce the issue. Maybe try if problem also exists with some other browser (which browser are you using?). Furthermore, for reproducing the issue it would be helpful if you could attach a screenshot of the configuration dialog (before saving the settings by clicking "Okay").
-
Do problem persists if the "Custom header/footer configuration" checkbox is checked? yes, because setting for even pages is kept and obeyed as wanted, but not for odd content pages :(
-
Maybe it helps to add the -Djava.awt.headless=true after restarting the server, i.e. executing /etc/init.d/tomcat8, which sets $JAVA_OPTS the problem seems to be gone :) Nevertheless some additional information: java version "1.7.0_111" OpenJDK Runtime Environment (IcedTea 2.6.7) (7u111-2.6.7-2~deb8u1) OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode) Does the export abort every time or only with specific content or with specific output settings? if no image is contained the export works, but...
-
Maybe it helps to add the -Djava.awt.headless=true I fear I need some pointers where to put your suggestion into conf/system.xml or alike ... Meanwhile some more information: java version "1.7.0_111" OpenJDK Runtime Environment (IcedTea 2.6.7) (7u111-2.6.7-2~deb8u1) OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode) Does the export abort every time or only with specific content or with specific output settings? if no image is contained the export works, but not for an image contained ... Did...
-
Could you please check if problem also exists if the "Custom header/footer configuration" checkbox is checked. Normally, if this checkbox is unchecked, then input fields should be disabled. But due to a bug user can fill the input fields although the "Custom header/footer configuration" checkbox is unchecked. In that case the entered values may not be stored.
-
A partially emphasized image title is currently not supported. However in Docmenta 2.0 the HTML 5 figure and figcaption elements will be supported. Then it should be possible to create partially emphasized image titles.
-
A partially emphasized image title is currently not supported. However in Docmenta 2.0 the HTML 5 and elements will be supported. Then it should be possible to create partially emphasized image titles.
-
Hi, Are you running Linux without graphical user interface? If yes, this could cause the problem. Maybe it helps to add the -Djava.awt.headless=true system property to the startup configuration of Tomcat. See also: https://stackoverflow.com/questions/5576986/servlet-giving-error-java-lang-noclassdeffounderror If this does not help, could you provide some more information. For example, what is the operating system and Java version you are running? Does the export abort every time or only with specific...
-
Hi, Are you running Linux without graphical user interface. If yes, this could cause the problem. Maybe it helps to add the -Djava.awt.headless=true system property to the startup configuration of Tomcat. See also: https://stackoverflow.com/questions/5576986/servlet-giving-error-java-lang-noclassdeffounderror If this does not help, could you provide some more information. For example, what is the operating system and Java version you are running? Does the export abort every time or only with specific...
-
Obviously an partial emphasized image title (due to <img class="align-center" id="myPic" src="../image/myPic" title="<em>myPic</em>"/>) is impossible :( After replacing title by "'myPic'" it works like a charm ... The appropriate error message from tomcat's log file could be SystemId Unknown; Line #6; Column #51; The value of attribute "title" associated with an element type "img" must not contain the '<' character. SystemId Unknown; Line #-1; Column #-1; Premature end of file. Does it indicate a...
-
HTML output aborts due to chunk computing
-
PDF output fails without error message
-
Custom header/footer configuration for PDF output not saved completely
-
eric revollo created ticket #53
page-break-condition not working at a root level
-
Thanks, for the feedback.
-
Hi, This is caused by the double quotes in the font-name. Unfortunately the double-quotes are not correctly escaped. This is a bug and will be fixed with next Docmenta version. (For some reason Firefox automatically removes the double-quotes). As a workaround, please replace the double quotes by single quotes. For example, replace "Courier New" by 'Courier New'.
-
Ladislav Lencucha created ticket #52
Output configuration "default" does not use styles
-
It works, thanks! Br, Ladislav
-
Ronald Krause posted a comment on ticket #50
You are right, I pasted images. I tried this on a few test pages and it worked, including HTML and PDF export. It still works with WebHelp export. But many thank for pointing out the cause. Docmenta is great product. Best Regards, Ronald
-
It seems that you have inserted the images by pasting the image from the clipboard into the content editor. This way the image is directly encoded in the HTML source using base64 encoding. Currently, Docmenta does not support this. Instead in the content editor the image URL has to be provided in the format "image/alias", where alias is the image alias (i.e. the image-filename without extension). For example, to insert a new image, you first have to upload the image-file to a image-folder. Then in...
-
Hi, The minimum number of characters before and after a hyphen can be defined in the "gentext.properties" file. To change the value, open the product in Docmenta and edit the "gentext.properties" file, which is located in the "System" folder. Change the values of the "hyphenation-push-character-count" and/or "hyphenation-remain-character-count". For example, change the value from 2 to 3: hyphenation-push-character-count=3 hyphenation-remain-character-count=3 Save the edited "gentext.properties" file....
-
Hi, The minimum number of characters before and after a hyphen can be defined in the "gentext.properties" file. To change the value, open the product in Docmenta and edit the "gentext.properties" file, which is located in the "System" folder. Change the values of the "hyphenation-push-character-count" and/or "hyphenation-remain-character-count". For example, change the value from 2 to 3: hyphenation-push-character-count=3 hyphenation-remain-character-count=3 Save the edited "gentext.properties" file....
-
End of line Hyphenation switch
-
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello Mr. Paula, thank you for very fast reaction. Below more details, in short: - there are warnings and errors about "invalid img src" - the tomcat error shows StackOverflow errors - changins export configuration does not change the problem - publishing as Webhelp works (0 Errors 0 Warnings). Greetings from Freibug, Ronald Krause Here the outputs in detail: Consistency...
1 >
