|
|
|
|
@ -6,8 +6,8 @@
|
|
|
|
|
<rect>
|
|
|
|
|
<x>0</x>
|
|
|
|
|
<y>0</y>
|
|
|
|
|
<width>742</width>
|
|
|
|
|
<height>573</height>
|
|
|
|
|
<width>747</width>
|
|
|
|
|
<height>617</height>
|
|
|
|
|
</rect>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="windowTitle">
|
|
|
|
|
@ -122,7 +122,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="engineInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Select rendering method according to your needs. <span style=" font-weight:600;">Software rendering</span> is much slower than hardware accelerated rendering using <span style=" font-weight:600;">OpenGL rendering</span>, but it works when OpenGL is not available at your platform. OpenGL rendering is selected as default and is recommended.</p><p>OpenGL rendering uses<span style=" font-weight:600;"> multisample antialiasing (MSAA)</span>, which provides good quality antialiasing. You can turn this feature on or off, but without antialiasing, bad quality image can occur. Samples count affect how much samples per pixel are considered to determine pixel color. It can be a value 1, 2, 4, 8, and 16. Most modern GPUs support at least value 8. Lower this value, if your GPU doesn't support the desired sample count.</p><p><span style=" font-weight:600;">Prefetch pages </span>prefetches (pre-renders) pages next to currently viewed pages, to avoid flickering during scrolling. Prefetched pages are stored in the page cache.</p><p><span style=" font-weight:600;">Multithreading strategy </span>defines how program will use CPU cores. Engine can use multiple cores. Strategy defines, how engine will use these cores. <span style=" font-weight:600;">Single thread</span> strategy uses only one CPU core for rendering page, and for some operations, they aren't parallelized, at the cost of more time needed for operation to be finished. But still, each page will use its own thread to be compiled/drawn. On the other side, there are two multithreading strategies, former is load balanced, latter uses maximum threads. Load balanced strategy parallelizes only pages, but not processing each individual page content, while maximum threads strategy will spawn as much threads as possible to process operations to achieve best performance.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>Choose a rendering method based on your needs. Although <span style=" font-weight:600;">Software Rendering</span> is slower than the hardware-accelerated <span style=" font-weight:600;">OpenGL Rendering</span>, it can be utilized when OpenGL is not available on your platform. The default (and recommended) method is OpenGL Rendering. </p><p>OpenGL rendering employs <span style=" font-weight:600;">Multisample Antialiasing (MSAA)</span>, ensuring high-quality image rendering. You have the option to enable or disable this feature. However, disabling it might lead to inferior image quality. The Samples Count sets the number of samples per pixel used to determine pixel color. It can be set to 1, 2, 4, 8, or 16. Most modern GPUs support at least a value of 8. If your GPU doesn't support the desired sample count, lower this value. </p><p>The <span style=" font-weight:600;">Prefetch Pages</span> feature pre-renders pages adjacent to the currently viewed pages, minimizing flickering during scrolling. Prefetched pages are stored in the page cache. </p><p>The <span style=" font-weight:600;">Multithreading Strategy</span> determines how the program will utilize CPU cores. With the <span style=" font-weight:600;">Single Thread</span> strategy, only one CPU core is used for rendering a page. This results in longer processing times, but each page is independently compiled/drawn in its own thread. Alternatively, there are two multithreading strategies: Load Balanced and Maximum Threads. Load Balanced only parallelizes pages without processing individual page content. In contrast, the Maximum Threads strategy spawns as many threads as possible for operations to achieve optimal performance. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -272,7 +272,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="renderingInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Rendering settings defines, how rendering engine should handle the page content, and appearance of displayed graphics. <span style=" font-weight:600;">Antialiasing</span> turns on antialiasing of painted shapes, such as rectangles, vector graphics, lines, but it did not affects text (characters printed on the screen). <span style=" font-weight:600;">Text antialiasing </span>turns on antialiasing of painted characters on the screen, but not any other items. Both <span style=" font-weight:600;">Antialiasing </span>and <span style=" font-weight:600;">Text antialiasing </span>affects only software renderer. If you are using hardware rendering engine, such as OpenGL rendering engine, this doesn't do anything, because OpenGL engine renders the pictures using MSAA antialiasing (if turned on).</p><p><span style=" font-weight:600;">Smooth pictures</span> transforms pictures to device space coordinates using smooth image transformation, which usually leads to better image quality. When this is turned off, then default fast transformation is used, and quality of the image is lower, if the source DPI and device DPI is different.</p><p><span style=" font-weight:600;">Ignore optional content </span>ignores all optional content settings and paints everything in the content stream. <span style=" font-weight:600;">Clip to crop box</span> clips the drawing rectangle to the crop box of the page, which is usually smaller, than whole page. The graphics outside of the crop box is not drawn (for example, it can contain marks for printer etc.). <span style=" font-weight:600;">Display page compile/draw time </span>is used mainly for debugging purposes, it displays page compile time (compiled page is stored in the cache) and draw time (when the renderer draws compiled page contents to the output device).</p><p><span style=" font-weight:600;">Display annotations</span> is used to enable or disable displaying of annotations. If annotations are disabled (they are not displayed), user can't interact with them.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>The rendering settings control how the rendering engine handles page content and the appearance of displayed graphics. <span style=" font-weight:600;">Antialiasing</span> smooths out the appearance of painted shapes, such as rectangles, vector graphics, and lines, but doesn't affect text. <span style=" font-weight:600;">Text antialiasing</span>, on the other hand, refines the appearance of text characters, leaving other items untouched. Both <span style=" font-weight:600;">Antialiasing </span>and <span style=" font-weight:600;">Text antialiasing </span>are relevant only for the software renderer. If you're using a hardware rendering engine like OpenGL, these settings won't have an impact because OpenGL renders images using MSAA antialiasing (if enabled). </p><p><span style=" font-weight:600;">Smooth pictures</span> option enables pictures to be transformed into device space coordinates using a high-quality image transformation method. This generally results in better image quality. When disabled, a default fast transformation is used, potentially reducing image quality if the source DPI and device DPI differ. </p><p><span style=" font-weight:600;">Ignore optional content </span>ignores all optional content settings and renders everything in the content stream. <span style=" font-weight:600;">Clip to crop box</span> restricts the rendering area to the page's crop box, which is usually smaller than the whole page. Graphics outside the crop box aren't drawn, which can be useful for removing printer marks and similar elements. <span style=" font-weight:600;">Display page compile/draw time</span> can be handy for debugging, showing the time taken to compile a page (stored in the cache) and the time taken to render the compiled page contents onto the output device. </p><p>Using the <span style=" font-weight:600;">Display annotations</span> setting, you can enable or disable the display of annotations. If annotations are disabled, the user will not be able to interact with them. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -402,7 +402,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="shadingInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Shading is meshed according the mesh quality criteria. It involves <span style=" font-weight:600;">color tolerance</span> and shape tolerance. If color of vertices of triangle in the mesh is too different (it differs more than color tolerance) then mesh is refined and triangle is subdivided. Some shadings are defined by patterns (such as <span style=" font-style:italic;">Coons patch shading </span>or <span style=" font-style:italic;">Tensor product patch shading</span>), which is also considered in meshing.</p><p><span style=" font-weight:600;">Preferred mesh resolution ratio</span> should be set to optimal balance between performance of mesh generation and quality of the mesh. Optimal triangle size will be computed in the following way: total meshing area (typically a page) will be multiplied with this ratio and that will determine the triangle size. So, if we have A4 page (210 mm x 297mm), and ratio is set to 0,01, then we will get optimal triangle size as 297 * 0.01 = ~3mm.</p><p><span style=" font-weight:600;">Minimal mesh resolution ratio</span> is ratio, which will determine triangle minimal size. At this bound, no triangles are subdivided, even if color is different or shape is not good. This should be set to a value, at which user barely can recognize patterns on the screen (for example, the size of triangle should be &lt; 1mm). But it also affect performance, because too much triangles can be generated.</p><p><span style=" font-weight:600;">Color tolerance</span> is threshold, at which is two colors recognized as different. The comparation is done component-wise, so if at least one of color components is greater than this parameter, then colors are treated as different.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>Shading is executed according to mesh quality criteria, involving <span style=" font-weight:600;">color tolerance</span> and shape tolerance. If the color of the vertices of a triangle in the mesh is too different (exceeding the set color tolerance), then the mesh is refined, and the triangle is subdivided. Some shadings are defined by patterns, such as <span style=" font-style:italic;">Coons patch shading</span> or <span style=" font-style:italic;">Tensor product patch shading</span>, which are also taken into consideration during meshing. </p><p>The <span style=" font-weight:600;">Preferred mesh resolution ratio</span> should be set to optimize the balance between the performance of mesh generation and the quality of the mesh. The optimal triangle size is computed as follows: the total meshing area (typically a page) is multiplied by this ratio to determine the triangle size. For example, if we have an A4 page (210 mm x 297 mm), and the ratio is set to 0.01, then the optimal triangle size is computed as 297 * 0.01 = ~3 mm. </p><p>The <span style=" font-weight:600;">Minimal mesh resolution ratio</span> is a ratio that determines the minimal triangle size. At this boundary, no triangles are subdivided, regardless of color variation or shape quality. This ratio should be set to a value at which a user can barely recognize patterns on the screen (for example, the triangle size should be &lt; 1 mm). However, this also affects performance, as too many triangles can be generated. </p><p><span style=" font-weight:600;">Color tolerance</span> is the threshold at which two colors are recognized as different. The comparison is done component-wise, so if at least one color component exceeds this parameter, the colors are treated as different. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -540,7 +540,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="cacheInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Rendering engine first compiles page for fast drawing, and then stores them in the cache. Stored compiled pages are usually drawn much faster than direct drawing. <span style=" font-weight:600;">Compiled page cache size</span> sets limits for compiled pages in kB. This limit should be at least two times large than largest compiled page size. If compiled page can't be inserted, then error is displayed during rendering. The higher this value is set, the faster the engine will be, at the cost of consumed operating memory.</p><p>Also, there is cache for thumbnails images. <span style=" font-weight:600;">Thumbnail image cache size </span>determines, how much space there is for thumbnail images. Set this value to at least fill space for thumbnails images on the screen. Again, the higher value is, the faster displaying of thumbnails is, at the cost of consumed operating memory. Thumbnails are stored as bitmaps for fast drawing, not as precompiled pages.</p><p>During rendering, fonts are cached. There is a two-level cache, one for general fonts, one for instanced fonts (fonts with given size). The <span style=" font-weight:600;">cached font limit</span> sets font cache limit (number of fonts) which can be stored in the cache. The <span style=" font-weight:600;">instanced font cache limit</span> sets font cache limit for instanced fonts (number of fonts with determined size), which can be stored in the cache. When cache limit is exceeded, then fonts are erased from the cache, but only if no operation in another thread is performed (for example, compiling pages), to avoid race conditions.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>The rendering engine first compiles the page to enable quick drawing and then stores these compiled pages in a cache. These stored pages usually render much quicker than non-cached pages. The <span style=" font-weight:600;">Compiled Page Cache Size</span> sets the memory limit for these compiled pages, measured in kilobytes. Ideally, this limit should be at least twice as large as the size of the largest compiled page. If a compiled page exceeds this limit, an error will be displayed during rendering. Setting a higher value for this limit can speed up the rendering engine, but it will consume more operating memory. </p><p>There is also a cache for thumbnail images. The <span style=" font-weight:600;">Thumbnail Image Cache Size</span> determines the memory space allocated for these images. This value should be set large enough to accommodate all thumbnail images on the screen. The larger this value is, the quicker thumbnails will display, but at the cost of consuming more operating memory. Please note that thumbnails are stored as bitmaps for rapid drawing, not as precompiled pages. </p><p>During rendering, fonts are cached as well. There are two levels of cache for fonts: one for general fonts and one for instance-specific fonts (fonts at a specific size). The <span style=" font-weight:600;">Cached Font Limit</span> sets the maximum number of fonts that can be stored in the cache. The <span style=" font-weight:600;">Instanced Font Cache Limit</span> sets the maximum number of instance-specific fonts that can be stored. If these cache limits are exceeded, fonts are removed from the cache. However, this only happens when no operation in another thread (like compiling pages) is being performed to avoid race conditions. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -767,7 +767,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="cmsInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p><span style=" font-weight:600;">Color management system </span>manages input and output color profiles and color transformations. It enables to perceive real colors defined in PDF document. Select 'Generic' to disable this functionality for fast color transform. <span style=" font-weight:600;">Rendering intent</span> affects how colors are transformed. Rendering intents are usually defined in content streams in PDF document, but you can override them, if you select other intent, than 'Auto'. <span style=" font-weight:600;">Accuracy </span>affects how precise the color transformation would be, at the cost of more memory consumption. <span style=" font-weight:600;">Black point compensation</span> compensates black colors out of gamut. <span style=" font-weight:600;">White paper color transformed </span>affects color of the underlying white paper - it transforms pure white from device RGB profile to output profile, if enabled.</p><p><span style=" font-weight:600;">Output color profile</span> defines output (target) rendering profile. This profile should be color space, in which your screen is displaying colors. You can also define color spaces for <span style=" font-weight:600;">gray/RGB/CMYK</span> device color spaces, which are used to transform gray/RGB/CMYK colors to the output color profile.</p><p>Document can contain output intents, which can be used for transforming between color spaces. If option <span style=" font-weight:600;">Consider document output intents</span> is checked, color management system checks, if document contains output intents, and if yes, then they are used for color transformation as device color spaces (gray/RGB/CMYK).</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>The <span style=" font-weight:600;">Color Management System</span> governs input and output color profiles and color transformations. This system allows for accurate color representation as defined in the PDF document. For faster color transformations, select 'Generic' to disable this functionality. The <span style=" font-weight:600;">Rendering Intent</span> selection influences the way colors are transformed. While rendering intents are often defined within the PDF document's content streams, you have the option to override them by selecting a different intent from 'Auto'. The <span style=" font-weight:600;">Accuracy</span> setting determines the precision of the color transformation, with higher accuracy consuming more memory. The <span style=" font-weight:600;">Black Point Compensation</span> adjusts for black colors that fall outside the gamut. The <span style=" font-weight:600;">White Paper Color Transformed</span> setting affects the color of the underlying white paper - enabling this will transform pure white from the device RGB profile to the output profile. </p><p>The <span style=" font-weight:600;">Output Color Profile</span> specifies the output (target) rendering profile. This profile should align with the color space that your screen uses to display colors. Additionally, you can set the color spaces for <span style=" font-weight:600;">gray/RGB/CMYK</span> device color spaces. These are used to transform gray/RGB/CMYK colors to the output color profile. </p><p>A document may contain output intents, which can be used for transforming between color spaces. If the <span style=" font-weight:600;">Consider Document Output Intents</span> option is checked, the color management system will verify whether the document contains output intents. If such intents are present, they will be used for color transformation as device color spaces (gray/RGB/CMYK). </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -847,7 +847,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="securityInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>If launch of application is allowed, then, after <span style=" font-weight:600;">Launch</span> action is triggered, message box appears, which asks the user, if he wants to execute external application. If user confirms the dialog, then external application is executed (for example, by windows function <span style=" font-weight:600;">ShellExecute</span>). When this option is turned off, then no dialog appears and external application is never executed.</p><p>If <span style=" font-weight:600;">URI link </span>launch is allowed, then, again, message box appears and asks the user, if he wants to open the URI link. If user confirms the dialog, then URI link is opened by standard web browser (or standard application, if URI links to the file system).</p><p>User should be really carefull with these settings, and only confirm the execution, if the document is safe, i.e. it comes from reliable source. Launching external applications and following URI links can be harmfull to the user's computer.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>If the application launch is permitted, a message box appears after the <span style=" font-weight:600;">Launch</span> action is triggered, asking the user if they want to execute an external application. If the user confirms the dialog, the external application executes (for example, using the Windows function <span style=" font-weight:600;">ShellExecute</span>). When this option is turned off, no dialog appears and the external application never executes. </p><p>If the <span style=" font-weight:600;">URI link</span> launch is allowed, a message box appears asking the user if they want to open the URI link. If the user confirms the dialog, the URI link is opened by the default web browser (or default application if the URI links to the file system). </p><p>Users should exercise caution with these settings and only confirm execution if the document is safe and comes from a reliable source. Launching external applications and following URI links can pose risks to the user's computer. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -1002,7 +1002,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="uiInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Maximum count of recent files controls, how much of recent files will be displayed in menu. When document is opened, then document is addet to the top of recent file list, and recent file list is truncated from bottom, if number of recent files is greater, than maximum.</p><p><span style=" font-weight:600;">Magnifier tool settings </span>set the appearance of the magnifier. Magnifier tool magnifies area under the mouse cursor. You can specify how big the magnifier will be (in <span style=" font-weight:600;">logical</span> pixels) and how much it will zoom.</p><p>By specifying <span style=" font-weight:600;">undo/redo</span> step count, you can control how many undo/redo steps is available when editing document. Set maximum undo step count to zero to disable undo/redo. You can also set undo step count to nonzero and redo step count to zero. In this case, redo actions will not be available, only undo actions. Changes are optimized for memory usage, so each undo/redo steps shares common unmodified objects between them (so, by guessestimate, 10 modifications of 50 MB document can take 51 MB of memory). Memory usage depends on how big changes are, but usually only small changes are done (for example, editing form field, modifying annotation affects small number of objects).</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>The 'Maximum count of recent files' setting controls the number of recent files displayed in the menu. When a document is opened, it is added to the top of the recent files list. The list is then truncated from the bottom if the number of recent files exceeds the maximum. </p><p><span style=" font-weight:600;">Magnifier tool settings</span> determine the appearance of the magnifier. The magnifier tool enlarges the area under the mouse cursor. You can specify the size of the magnifier (in <span style=" font-weight:600;">logical</span> pixels) and its zoom level. </p><p>By specifying the <span style=" font-weight:600;">undo/redo</span> step count, you control the number of undo/redo steps available during document editing. Setting the maximum undo step count to zero disables the undo/redo function. You can also set a nonzero undo step count and a zero redo step count, which would make only undo actions available, with redo actions disabled. Changes are optimized for memory usage, so each undo/redo step shares unmodified objects with others. This means that, roughly speaking, making 10 modifications to a 50 MB document may consume around 51 MB of memory. Actual memory usage depends on the extent of the changes but is usually minimal as changes typically affect a small number of objects (for example, editing a form field or modifying an annotation). </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -1132,7 +1132,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="speechInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Set speech settings to enable document reading. These settings are default settings for text to speech functionality, but some can be changed later. Pitch can have values from -1.0 to 1.0 and 0.0 is default. Rate can also have values ranging from -1.0 to 1.0, while 0.0 is normal speech flow. Volume can have values from 0.0 to 1.0.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>Configure the speech settings to enable the text-to-speech feature for reading documents. While these settings act as defaults for the text-to-speech function, some can be adjusted later on. The 'Pitch' setting can vary from -1.0 to 1.0, with 0.0 serving as the default value. Similarly, the 'Rate' can range from -1.0 to 1.0, with 0.0 denoting a normal speech flow. Lastly, 'Volume' can be adjusted between 0.0 and 1.0. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -1212,7 +1212,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="formInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Form field appearance settings can be used to set highlighting of editable form fields. Required form fields can be highlighted separately by red color, other fields can be highlighted by blue color.</p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>You can customize the appearance of form fields using the provided settings, including the option to highlight editable fields. You can separately highlight required form fields in red, while other fields can be emphasized in blue. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
@ -1372,7 +1372,7 @@
|
|
|
|
|
<item>
|
|
|
|
|
<widget class="QLabel" name="signatureInfoLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string><html><head/><body><p>Settings for verification of digital signatures. Digital signatures are verified as strict, as possible, to avoid any malicious content or signature manipulation. Verification can also be turned off, if it is not wanted. When <span style=" font-weight:600;">Strict mode</span> is turned on, every warning is treated as error. You can also ignore certificate expiration date, but do this only, if you know what you are doing, because it is dangerous. For verification, list of trusted certificates is used. System certificates can be inserted into the list, and also you can manage your own list of trusted certificates. </p></body></html></string>
|
|
|
|
|
<string><html><head/><body><p>These are the settings for digital signature verification. Digital signatures are verified as strictly as possible to prevent any malicious content or signature manipulation. Verification can also be disabled, if not required. When <span style=" font-weight:600;">Strict mode</span> is enabled, every warning is treated as an error. You have the option to ignore the certificate expiration date, but this should only be done if you fully understand the potential risks involved. Verification uses a list of trusted certificates. System certificates can be added to this list, and you can also manage your own list of trusted certificates. </p></body></html></string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="wordWrap">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
|
Jakub Melka