Jump to content
You must now use your email address to sign in [click for more info] ×

Pyanepsion

Members
  • Posts

    926
  • Joined

3 Followers

Profile Information

  • Location
    La Région Auvergne-Rhône-Alpes
  • Member Title
    Communication littéraire

Recent Profile Visitors

2,938 profile views
  1. Hello, @Artvarkve11, Now's the time : Spring Sales. Enjoy yourselves.
  2. The problem is different from what was mentioned in previous discussions. @DebSki, as Jon P’s reply suggested, by not reproducing the bug without the linked files, the reason was here the linked Affinity files in a old version. By reregistering each of the 51 files with the new version of the suite, the file ‘freeze.afpub’ now opens correctly. @Jon P, The bug can be reproduced. I have created a new archive using the old versions of the linked parts, some of which sometimes contain another file themselves. I’ve anonymized the main file and then sorted the old linked files by type: afdesign, afpub, jpg, png, svg, xlsx. There’s another problem: linked afdesign images that are pinned in the templates are no longer pinned in the pages using those templates.
  3. @Jon P I sent the AFPUB file (without the images or the data merge file), and a video showing the screen freezing.
  4. Hey, @Chris B, I can provide files and a recording, but only on a confidential and private basis. The bug does not appear on version 2.3.1.2217. and is reversible after a considerable time after each opening. No key combination on the keyboard seems to resolve this malfunction.
  5. V2.4.02301 Hello everyone, I have encountered a significant performance problem when using the new production version. I have taken a 63 page document containing 13 layouts, a good number of pinned objects and a data merge file. After successfully opening the document on the last modified page, I wanted to navigate to other pages. I then found that I couldn't select an object, edit text or even activate a page. I initially suspected a software acceleration problem, but this proved to be incorrect. The document takes a considerably long time to load. I stopped timing after 18 minutes, which is in stark contrast to the performance observed on the previous 2.3.1 version of the software where it only takes a few seconds. I came back after eating, and the software was finally unblocked. The same thing happens every time the file is opened. This is obviously a major bug. Thank you in advance for your attention to this matter. I remain at your disposal for any further information you may require.
  6. v2.3.1.2217 Hello everyone, I initially had a suggestion for improvement in mind. However, I'm now convinced that it was more of a design error. In Affinity Publisher it was originally a text box containing a letter and three coloured backgrounds, as well as a rectangle measuring 7 × 84 pixels, embedded in an area measuring 320 × 84 pixels. During the process in Affinity, numerous nested groups were created, and all the objects were initially provided in reduced size, and then successively moved and enlarged horizontally and vertically. For example, our vertical rectangle now measures 18.243 × 184.069 pixels before being reduced by a subsequent transformation. There is even an unnecessary group. After optimizing 48 similar files, I saw an average reduction in size of at least 40% per file, accompanied by a significant reduction in the processing time needed to perform unnecessary calculations. Longer text span, Use hex colors (and here Add line breaks for explanations). <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="427px" height="112px" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;"> <g transform="matrix(1.33333,0,0,1.33333,0,0)"> <g transform="matrix(0.383705,0,0,0.45635,0,0)"> <rect x="0" y="0" width="18.243" height="184.069" style="fill:#509e2f;"/> </g> <g transform="matrix(1,0,0,0.466667,0,0)"> <g transform="matrix(1,0,0,2.14286,0,0)"> <rect x="80.549" y="35.619" width="1.667" height="6.703" style="fill:#509e2f;"/> <rect x="272.484" y="35.619" width="1.667" height="6.703" style="fill:#509e2f;"/> <rect x="13.837" y="41.815" width="1.667" height="6.703" style="fill:#509e2f;"/> </g> <g transform="matrix(1,0,0,2.14286,0,0)"> <text x="10.5px" y="41.051px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:6px;">In hac habitasse platea : «</text> <text x="82.216px" y="41.051px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:6px;">Mauris rutrum enim vitae, Mauris ?</text> <text x="175.775px" y="41.051px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:6px;fill:#509e2f;">C</text> <text x="180.108px" y="41.051px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:6px;">’ed pretium ante sit amet elit tellus. » Ut viverra :</text> <g transform="matrix(6,0,0,6,152.561,47.2471)"> </g> <text x="10.5px" y="47.247px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:6px;">« Maecenas quis magna. Ut viverra nisl eu ipsum […]</text> </g> </g> </g> </svg> svg-optimized.svg svg-optimized.afpub
  7. 😁 It’s a good thing that computer science isn’t of Swedish (flat) or Lithuanian (vietą) origin, otherwise we’d certainly be in trouble! Renowned dictionaries Larousse and Le Robert clearly state that ‘spot’ is considered a foreign word, not a French one. They simply indicate their translation. Similarly, the Centre National de Ressources Textuelles et Lexicales (CNRTL) only ever provides an exhaustive lexicon of words found in printed documents (from 1880 to 1980 for spot, peaking in 1970, and not beyond), and does not consider them to be French terms at all. For example, it lists words such as ‘software’ that no French speaker uses any more. An analysis of the evolution of the word ‘spot’ in French literature shows its emergence around 1600, its growing popularity in the 1930s with the advent of advertising, and then a decline until the 1950s, marked by the Second World War. There was a further decline until the 1980s, when computer technology revived interest in the term. Since 2015, however, its use has been declining. Prominent figures in French lexicography such as Paul Robert, Émile Littré and Alain Rey, members of the Académie française, did not recognize these terms as an integral part of the French language. The dictionary of the Académie française, the reference for the French language, does not recognize ‘spot’ as a French term. In 2017, it recommended avoiding anglicisms where French terms exist, advocating the use of ‘projecteur’ for software such as PhotoShop and Blender.
  8. I don’t quite agree on this point! Why complicate users’ understanding with foreign terms like ‘spot’ and ‘dot’, which don’t exist in French and require learning, when there are terms in French that everyone can understand: ‘Projecteur’ and ‘Point’? More and more reference software, such as Photoshop, Blender and many others, are now adopting a true French version, without foreign term, because they have realized that this allows them to broaden their customer base to include beginners. It would be regrettable if the Affinity suite were to adopt a retrograde position on this issue.
  9. I can confirm that. On the other hand, ‘Spot’ does not exist in the French language, although it is often used in various technical fields. In physics, it refers to a point of light, or more precisely a spot moving on a graduated scale, produced by a measuring instrument with a rotating mirror. This would be an oscilloscope, for example. In the entertainment sector, it is a small adjustable projector with a reduced light beam used for spot lighting on a stage, in a shop window or in an art gallery. The Affinity suite help explains in French : Blender, for its part, offers: Lumière ponctuelle (Point Light) : A point light is a light source that emits rays of light in all directions from a single point in space. It creates sharp shadows and is often used to simulate light sources such as light bulbs or candles. Projecteur (Spot Light) : A spotlight is a light source that emits a beam of light in a specific direction, at a defined angle. This light is often used to simulate car headlights, stage lights or torches. Lumière du soleil (Sun Light) : Sunlight is a directional light source that simulates natural sunlight. It emits parallel rays of light that pass evenly through the space. This light is used to simulate outdoor lighting and creates consistent, soft shadows. Lumière de zone (Area Light) : A zone light is a light source that has an extended size and shape rather than a point or beam. It emits light in all directions from its surface, creating soft shadows and more natural lighting effects. Area lights are often used to illuminate large surfaces or to simulate light sources such as windows or light panels. A good translation in French of 'Spot' would be 'projecteur' (projector) as in the famous Blender, 'phare' (lighthouse) or 'lampe-torche' (flashlight).
  10. Hello everyone, No matter how many times I click on ’Relative coordinates’ when exporting, I don’t get the expected result. How can I create relative coordinates when exporting SVG text? I would like to obtain: <text dx="eee" dy="ccc"> instead of <text x="aaa" dy="bbb"> Thank you for your explanations.
  11. Please note. I was talking about ‘ko’ and ‘PPP’ as they should be written in French, otherwise they mean something else. Wikipédia : Point par pouce, Octet
  12. Version: 2.4.0.2256 Hello everyone, I would like to point out a serious problem with the translation of export parameters in SVG format. It's not just a matter of errors in meaning, but sometimes results in inconsistent or even incomprehensible translations. I personally spent a considerable amount of time trying to understand the optimisation options, before finally turning to Sean P.'s enlightened explanations, which led me to revert to the English version for greater clarity. In addition, there seems to be a duplication of the options "Export text as curve", which adds to the confusion. In the attached document, questionable translations are highlighted in orange, while those requiring immediate revision are marked in red. Below is a translation proposal that is more in line with professional standards. 🔴Export text as curve for font independence = Exporter le texte en courbes pour l’indépendance des fontes (or "Texte en courbe pour s’affranchir des fontes" if you don't solve the problem of the length of the chain.) 🔴kB = ko (note for the translator: both letters ko are in lower case) 🟡Downsample images = Rééchantillonnage des images 🟡Above DPI: = PPP au-delà de : (note for the translator: the three letters PPP are in capitals) 🟡Use DPI: = Résolution PPP : (note for the translator: the three letters PPP are in capitals) 🟡Export text as curves = Exporter le texte sous forme de courbes 🔴Longer text spans = Étendues de texte plus longues (note for the translator: the official W3C translation of "text span" is "Portion de texte", which is appropriate in most cases, "Travée de texte" is sometimes more precise, and "Étendue de texte" is often better suited to complex cases such as this). ✅Relative coordinates = Coordonnées relatives ✅Use hex colours = Utiliser des couleurs hexadécimales ✅Flattern transforms = Aplatir les transformations 🔴Use tile patterns = Utiliser des motifs de tuiles 🔴Set viewbox = Définir la zone d'affichage ✅Add line breaks = Ajouter des sauts de ligne
  13. Hi, @Sean P, Your explanation is pertinent. However, I can’t help thinking that there’s a bug when the text: produce this <tspan> which seems incongruous on ‘er’: <text x="14" y="50.065" style="font-family:'ArialMT','Arial',sans-serif;font-size:8px;fill:#101820">profonde. V<tspan x="54.922px 59.371px" y="50.065px 50.065px">er</tspan>s l’</text> I should point out that there is no spacing on ‘er’ here. I’ve found many errors of this type and others in the new AFPUB file that I was proposing to share.
  14. In order to make it easier to understand the problems encountered and to speed up the process of resolving bugs and improvements, I would, of course, be happy to share privately with the development team the 16-page AFPUB file I used to create the 16 SVG images for a web page, along with the optimized result expected. I hope that this sharing will help: Provide a more complete overview of a real situation. Highlight-specific problem areas. Clearly show the expected results. Save time by pointing out a large proportion of the problems encountered.
  15. v2.4.0.2256 Hello everyone, I've identified an issue with exporting text containing characters with a coloured background. The resulting SVG file has inappropriate conversion of superfluous <tspan> tags and even incongruous grouping, as illustrated, the attachment and source code provided below. In some cases, the file size is 10 times larger than it should be. This anomaly does have a significant impact on the size of the file generated and slows down its display considerably. <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 320 84" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;"> <g transform="matrix(1,0,0,0.466667,0,2.84217e-14)"> <g transform="matrix(1,0,0,2.14286,0,0)"> <rect x="38.895" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="72.691" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="98.918" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="120.711" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="162.066" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="191.855" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="214.977" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="223.426" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="249.652" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="293.234" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="312.797" y="32.423" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="22.441" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="60.242" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="83.367" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="92.262" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="129.621" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="150.52" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="173.641" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> <rect x="182.09" y="42.823" width="2.223" height="8.938" style="fill:#e43a30;"/> </g> <g transform="matrix(1,0,0,2.14286,0,0)"> <text x="14px" y="39.665px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:8px;fill:#101820;">Nullam hendrerit viverra dolor<tspan x="118.488px 120.711px 122.934px 127.828px 132.277px " y="39.665px 39.665px 39.665px 39.665px 39.665px ">. Ves</tspan>tibulum fringilla, lectus id viverra malesuada, enim</text> <g transform="matrix(8,0,0,8,201.648,50.0652)"> </g> <text x="14px" y="50.065px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:8px;fill:#101820;">mi adipiscing ligula, et bibendum lacus lectus id sem.</text> </g> </g> </svg> I have also noticed many times, in production with version 2.3.1.2217, similar malfunctions with the management of multiple spaces, but I have not managed to reproduce them conclusively in this report. svg-bug.afpub
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.