Pyanepsion

Sorry, but I don't understand your question.

@PixelEngineer, look at the values for the decoration. The value (+0.07 in 2.0.3 and not -0.07 in 2.0.0) for the bottom of the filling is not consistent with the other values.

I hadn't seen the tag.

😎This other topic (of which I am the author and to which I gave the link) concerns suggestions for improvements, but this is more of a bug since this problem would not be seen on the Mac, but only on the PC.

v 2.0.3.1688 Hello everyone. The Summary of Styles section would benefit from allowing the surface to be enlarged at will and to be copied and pasted for better use in the software itself and in another application. On Mac:

With Windows, as in version 2, in version 1 you could not enlarge the summary area with the mouse. You can only use the scroll bar, and it was impossible to copy the content. I think this has been reported before.

v 2.0.3.1688 Hello everyone. The Summary of Styles section would benefit from allowing the surface to be enlarged at will and to be copied and pasted for better use in the software itself and in another application.

v 2.0.3.1688 Hello everyone. The style palette is not displaying the correct text colour for both paragraph and character styles. This often makes the text unreadable in the palette as soon as there is a background on the text. What style is used on the second word on the yellow background (Vestibulum)?

I have found that this bug appears when a character style is created just before the first footnote (hence the description in the initial message), but not only. I first noticed it when I took an old file and created a new, somewhat similar book. Note also that this malfunction does not always appear: it seems to me, but I am not sure, that it may not appear when the new character style is not used on a page. The workaround is of course obvious, but it is time consuming, and there is a risk of forgetting (out of 200 notes I had forgotten 2). The important thing here is that this important bug is fixed.

Close the modified document and go back to the original document and add new notes. style-note.mp4

v. 2.0.3.1688. Hello everyone, footnote-color.afpub 1. Create a document that contains the paragraph styles Corps and Bas de page depending on the style Base, and the character style couleur-vert. 2. Write a bit of text in Corps paragraph style. 3. Select some words using the couleur-vert character style. 4. Add a footnote using the Bas de page paragraph style. The note will use the character style.

It is: U+200C = ZERO WIDTH NON-JOIN The ZERO WIDHT NON-JOIN (en français ANTILIANT SANS CHASSE) is not a space but a punctuation. It belongs to the general category Cz (a format control character). It is part of the General Punctuation subset (U+2000 to U+206F).

It would be consistent for all 17 Unicode characters referenced as space in the general category Zs (a space character of various non-zero widths) to be detected without going through a regex, with reservations about Ogham Mark Space: this character may be considered invisible even though it is visible (invisible: It is the absence of a character on the writing line of the ogham, visible: we see the line). I would opt for yes. As for the 43 characters in the Cf category (a format control character), it can be discussed for the 2 (but only 2 from general category Cf) that are zero width spaces. I would opt for yes, as these two null spaces sometimes cause layout problems.

Just use the information I have provided! 😂 In short! Some spaces are not detected (Red) by the usual sequence \s, others are detected (Green), but are not spaces as such, but something else. Example: - The character U+1361 ETHIOPIAN SPACE belongs to the general category Po (Punctuation, other). It is a word separator. It is not considered a space. - The character U+1680 OGHAM SPACE MARK is a visible line but without character. - The character U+303F IDEMOGRAPHIC HALF SPACE belongs to the general category So (Symbol, other). It visibly indicates a display cell 'padding' used when ideographic characters in a double-byte character set have been rendered as separate characters. It is not considered a space. etc.

Maybe you didn't see it. I was pointing out that there are a number of each type of character. Here is the complete list of Unicode characters with the name quotation apostrophe and spaces, but not all of them are actually considered as such. Apostrophe (8) U+0027 = APOSTROPHE U+0149 = LATIN SMALL LETTER N PRECEDED BY APOSTROPHE U+02BC = MODIFIER LETTER APOSTROPHE U+02EE = MODIFIER LETTER DOUBLE APOSTROPHE U+055A = ARMENIAN APOSTROPHE U+07F4 = NKO HIGH TONE APOSTROPHE U+07F5 = NKO LOW TONE APOSTROPHE U+FF07 = FULLWIDTH APOSTROPHE Quotation (26) U+0022 = QUOTATION MARK U+00AB = LEFT-POINTING DOUBLE ANGLE QUOTATION MARK U+00BB = RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK U+2018 = LEFT SINGLE QUOTATION MARK U+2019 = RIGHT SINGLE QUOTATION MARK U+201A = SINGLE LOW-9 QUOTATION MARK U+201B = SINGLE HIGH-REVERSED-9 QUOTATION MARK U+201C = LEFT DOUBLE QUOTATION MARK U+201D = RIGHT DOUBLE QUOTATION MARK U+201E = DOUBLE LOW-9 QUOTATION MARK U+201F = DOUBLE HIGH-REVERSED-9 QUOTATION MARK U+2039 = SINGLE LEFT-POINTING ANGLE QUOTATION MARK U+203A = SINGLE RIGHT-POINTING ANGLE QUOTATION MARK U+275B = HEAVY SINGLE TURNED COMMA QUOTATION MARK ORNAMENT U+275C = HEAVY SINGLE COMMA QUOTATION MARK ORNAMENT U+275D = HEAVY DOUBLE TURNED COMMA QUOTATION MARK ORNAMENT U+275E = HEAVY DOUBLE COMMA QUOTATION MARK ORNAMENT U+275F = HEAVY LOW SINGLE COMMA QUOTATION MARK ORNAMENT U+2760 = HEAVY LOW DOUBLE COMMA QUOTATION MARK ORNAMENT U+276E = HEAVY LEFT-POINTING ANGLE QUOTATION MARK ORNAMENT U+276F = HEAVY RIGHT-POINTING ANGLE QUOTATION MARK ORNAMENT U+2E+42 = DOUBLE LOW-REVERSED-9 QUOTATION MARK U+301D = REVERSED DOUBLE PRIME QUOTATION MARK U+301E = DOUBLE PRIME QUOTATION MARK U+301F = LOW DOUBLE PRIME QUOTATION MARK U+FF02 = FULLWIDTH QUOTATION MARK Space (21) U+0020 = SPACE U+00A0 = NO-BREAK SPACE U+1361 = ETHIOPIC WORDSPACE U+1680 = OGHAM SPACE MARK U+2002 = EN SPACE U+2003 = EM SPACE U+2004 = THREE-PER-EM SPACE U+2005 = FOUR-PER-EM SPACE U+2006 = SIX-PER-EM SPACE U+2007 = FIGURE SPACE U+2008 = PUNCTUATION SPACE U+2009 = THIN SPACE U+200A = HAIR SPACE U+200B = ZERO WIDTH SPACE U+202F = NARROW NO-BREAK SPACE U+205F = MEDIUM MATHEMATICAL SPACE U+2408 = SYMBOL FOR BACKSPACE U+2420 = SYMBOL FOR SPACE U+3000 = IDEOGRAPHIC SPACE U+303F = IDEOGRAPHIC HALF FILL SPACE U+FEFF = ZERO WIDTH NO-BREAK SPACE There are 18 kinds of real spaces, but not all of them are found without a complicated regex, hence the proposal of the checkbox feature. Searching does not necessarily mean replacing!

Apple’s last support date for this operating system released on 25 September 2017 ended in November 2020. Buy a new Mac, or take the opportunity to upgrade to more perennial hardware.

Hello @DesignNorth, If you include a file with illegal fonts, they will generally not be recognised correctly by the softwares. You should therefore proceed as MikeTo has indicated. If you see ’? Arial’, it means that this font has been strangely uninstalled from your operating system, or that your system uses a corrupted font. I invite you to reset all your fonts on your computer. Then install all the free fonts provided by the manufacturer of your operating system. In the meantime, you can paste all the text content of your 4 pages into an ASCII editor to remove all styles (including fonts, sizes, colours, etc.) and then copy the text from the ASCII editor into Affinity Publisher and start the formatting again.

Regex is not at all suitable when it comes to finding all occurrences of a large number of denominations that can each be written in a large number of ways. To continue the previous example of the denomination Alice’s Restaurant (a title of a film of Arthur Pen): alice's restaurant, Alice's restaurant, alice's Restaurant, Alice’s Restaurant alice’s restaurant, Alice’s restaurant, alice’s Restaurant, Alice’s Restaurant aliceʼs restaurant, Aliceʼs restaurant, aliceʼs Restaurant, Aliceʼs Restaurant It is obviously much more time-consuming to have to write a new Regex for each title searched than to use four clicks in the search options, once and for all, to satisfy everyone: Match Case (the only choice currently available) Match Space Match Quote Match Apostrophe As much as it would be abnormal if the software forced us to confuse upper and lower case, straight apostrophe and the 2 others, straight quote and the 14 others, normal space and the 16 others, it would be appalling if it did not allow us differentiate between them. @walt.farrellHere are some possibilities with Microsoft Word. By default. Match case

@loukash, I think you misunderstood the description. It’s a good thing that Affinity Publisher automatically (according to our settings) replaces the straight apostrophe with a typographical apostrophe, as this is the standard in most countries. It is a major malfunction, however, if Affinity Publisher does not show hits with a typographical quote when a straight quote is typed into the search box. What you are asking for should be an option in the search menu as for the differentiation of upper and lower case input. This would make it possible to find both occurrences of this short example. Here, only the case can be undifferentiated in the search, not the type of apostrophe or quotation mark.

Hello, @pirochan_whwm, There does seem to be an error either in the file or in its interpretation, as the formula is rotated by 180° and is offset from the origins. Enter in Affinity Designer abscissa 406.6 px instead of 407.2 px and ordinate 46.4 px instead of -9.1 px (i.e. like the width and height). <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <svg xmlns="http://www.w3.org/2000/svg" width="408.024px" height="43.424px" viewBox="0 -1449.5 22543.4 2399" xmlns:xlink="http://www.w3.org/1999/xlink" style=""> <defs> <path id="MJX-4-TEX-I-3B8" d="M35 200Q35 302 74 415T180 610T319 704Q320 704 327 704T339 705Q393 701 423 656Q462 596 462 495Q462 380 417 261T302 66T168 -10H161Q125 -10 99 10T60 63T41 130T35 200ZM383 566Q383 668 330 668Q294 668 260 623T204 521T170 421T157 371Q206 370 254 370L351 371Q352 372 359 404T375 484T383 566ZM113 132Q113 26 166 26Q181 26 198 36T239 74T287 161T335 307L340 324H145Q145 321 136 286T120 208T113 132Z"> </path> <path id="MJX-4-TEX-I-6D" d="M21 287Q22 293 24 303T36 341T56 388T88 425T132 442T175 435T205 417T221 395T229 376L231 369Q231 367 232 367L243 378Q303 442 384 442Q401 442 415 440T441 433T460 423T475 411T485 398T493 385T497 373T500 364T502 357L510 367Q573 442 659 442Q713 442 746 415T780 336Q780 285 742 178T704 50Q705 36 709 31T724 26Q752 26 776 56T815 138Q818 149 821 151T837 153Q857 153 857 145Q857 144 853 130Q845 101 831 73T785 17T716 -10Q669 -10 648 17T627 73Q627 92 663 193T700 345Q700 404 656 404H651Q565 404 506 303L499 291L466 157Q433 26 428 16Q415 -11 385 -11Q372 -11 364 -4T353 8T350 18Q350 29 384 161L420 307Q423 322 423 345Q423 404 379 404H374Q288 404 229 303L222 291L189 157Q156 26 151 16Q138 -11 108 -11Q95 -11 87 -5T76 7T74 17Q74 30 112 181Q151 335 151 342Q154 357 154 369Q154 405 129 405Q107 405 92 377T69 316T57 280Q55 278 41 278H27Q21 284 21 287Z"> </path> <path id="MJX-4-TEX-N-3D" d="M56 347Q56 360 70 367H707Q722 359 722 347Q722 336 708 328L390 327H72Q56 332 56 347ZM56 153Q56 168 72 173H708Q722 163 722 153Q722 140 707 133H70Q56 140 56 153Z"> </path> <path id="MJX-4-TEX-N-28" d="M94 250Q94 319 104 381T127 488T164 576T202 643T244 695T277 729T302 750H315H319Q333 750 333 741Q333 738 316 720T275 667T226 581T184 443T167 250T184 58T225 -81T274 -167T316 -220T333 -241Q333 -250 318 -250H315H302L274 -226Q180 -141 137 -14T94 250Z"> </path> <path id="MJX-4-TEX-N-32" d="M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z"> </path> <path id="MJX-4-TEX-N-2212" d="M84 237T84 250T98 270H679Q694 262 694 250T679 230H98Q84 237 84 250Z"> </path> <path id="MJX-4-TEX-N-29" d="M60 749L64 750Q69 750 74 750H86L114 726Q208 641 251 514T294 250Q294 182 284 119T261 12T224 -76T186 -143T145 -194T113 -227T90 -246Q87 -249 86 -250H74Q66 -250 63 -250T58 -247T55 -238Q56 -237 66 -225Q221 -64 221 250T66 725Q56 737 55 738Q55 746 60 749Z"> </path> <path id="MJX-4-TEX-I-3C0" d="M132 -11Q98 -11 98 22V33L111 61Q186 219 220 334L228 358H196Q158 358 142 355T103 336Q92 329 81 318T62 297T53 285Q51 284 38 284Q19 284 19 294Q19 300 38 329T93 391T164 429Q171 431 389 431Q549 431 553 430Q573 423 573 402Q573 371 541 360Q535 358 472 358H408L405 341Q393 269 393 222Q393 170 402 129T421 65T431 37Q431 20 417 5T381 -10Q370 -10 363 -7T347 17T331 77Q330 86 330 121Q330 170 339 226T357 318T367 358H269L268 354Q268 351 249 275T206 114T175 17Q164 -11 132 -11Z"> </path> <path id="MJX-4-TEX-N-2B" d="M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z"> </path> <path id="MJX-4-TEX-N-31" d="M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z"> </path> <path id="MJX-4-TEX-N-73" d="M295 316Q295 356 268 385T190 414Q154 414 128 401Q98 382 98 349Q97 344 98 336T114 312T157 287Q175 282 201 278T245 269T277 256Q294 248 310 236T342 195T359 133Q359 71 321 31T198 -10H190Q138 -10 94 26L86 19L77 10Q71 4 65 -1L54 -11H46H42Q39 -11 33 -5V74V132Q33 153 35 157T45 162H54Q66 162 70 158T75 146T82 119T101 77Q136 26 198 26Q295 26 295 104Q295 133 277 151Q257 175 194 187T111 210Q75 227 54 256T33 318Q33 357 50 384T93 424T143 442T187 447H198Q238 447 268 432L283 424L292 431Q302 440 314 448H322H326Q329 448 335 442V310L329 304H301Q295 310 295 316Z"> </path> <path id="MJX-4-TEX-N-69" d="M69 609Q69 637 87 653T131 669Q154 667 171 652T188 609Q188 579 171 564T129 549Q104 549 87 564T69 609ZM247 0Q232 3 143 3Q132 3 106 3T56 1L34 0H26V46H42Q70 46 91 49Q100 53 102 60T104 102V205V293Q104 345 102 359T88 378Q74 385 41 385H30V408Q30 431 32 431L42 432Q52 433 70 434T106 436Q123 437 142 438T171 441T182 442H185V62Q190 52 197 50T232 46H255V0H247Z"> </path> <path id="MJX-4-TEX-N-6E" d="M41 46H55Q94 46 102 60V68Q102 77 102 91T102 122T103 161T103 203Q103 234 103 269T102 328V351Q99 370 88 376T43 385H25V408Q25 431 27 431L37 432Q47 433 65 434T102 436Q119 437 138 438T167 441T178 442H181V402Q181 364 182 364T187 369T199 384T218 402T247 421T285 437Q305 442 336 442Q450 438 463 329Q464 322 464 190V104Q464 66 466 59T477 49Q498 46 526 46H542V0H534L510 1Q487 2 460 2T422 3Q319 3 310 0H302V46H318Q379 46 379 62Q380 64 380 200Q379 335 378 343Q372 371 358 385T334 402T308 404Q263 404 229 370Q202 343 195 315T187 232V168V108Q187 78 188 68T191 55T200 49Q221 46 249 46H265V0H257L234 1Q210 2 183 2T145 3Q42 3 33 0H25V46H41Z"> </path> <path id="MJX-4-TEX-N-2061" d=""> </path> <path id="MJX-4-TEX-S3-28" d="M701 -940Q701 -943 695 -949H664Q662 -947 636 -922T591 -879T537 -818T475 -737T412 -636T350 -511T295 -362T250 -186T221 17T209 251Q209 962 573 1361Q596 1386 616 1405T649 1437T664 1450H695Q701 1444 701 1441Q701 1436 681 1415T629 1356T557 1261T476 1118T400 927T340 675T308 359Q306 321 306 250Q306 -139 400 -430T690 -924Q701 -936 701 -940Z"> </path> <path id="MJX-4-TEX-I-69" d="M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z"> </path> <path id="MJX-4-TEX-I-6E" d="M21 287Q22 293 24 303T36 341T56 388T89 425T135 442Q171 442 195 424T225 390T231 369Q231 367 232 367L243 378Q304 442 382 442Q436 442 469 415T503 336T465 179T427 52Q427 26 444 26Q450 26 453 27Q482 32 505 65T540 145Q542 153 560 153Q580 153 580 145Q580 144 576 130Q568 101 554 73T508 17T439 -10Q392 -10 371 17T350 73Q350 92 386 193T423 345Q423 404 379 404H374Q288 404 229 303L222 291L189 157Q156 26 151 16Q138 -11 108 -11Q95 -11 87 -5T76 7T74 17Q74 30 112 180T152 343Q153 348 153 366Q153 405 129 405Q91 405 66 305Q60 285 60 284Q58 278 41 278H27Q21 284 21 287Z"> </path> <path id="MJX-4-TEX-S3-29" d="M34 1438Q34 1446 37 1448T50 1450H56H71Q73 1448 99 1423T144 1380T198 1319T260 1238T323 1137T385 1013T440 864T485 688T514 485T526 251Q526 134 519 53Q472 -519 162 -860Q139 -885 119 -904T86 -936T71 -949H56Q43 -949 39 -947T34 -937Q88 -883 140 -813Q428 -430 428 251Q428 453 402 628T338 922T245 1146T145 1309T46 1425Q44 1427 42 1429T39 1433T36 1436L34 1438Z"> </path> </defs> <g stroke="currentColor" fill="currentColor" stroke-width="0" transform="matrix(1 0 0 -1 0 0)"> <g data-mml-node="math"> <g data-mml-node="msub"> <g data-mml-node="mi"> <use xlink:href="#MJX-4-TEX-I-3B8"> </use> </g> <g data-mml-node="mi" transform="translate(469, -150) scale(0.707)"> <use xlink:href="#MJX-4-TEX-I-6D"> </use> </g> </g> <g data-mml-node="mo" transform="translate(1417.6, 0)"> <use xlink:href="#MJX-4-TEX-N-3D"> </use> </g> <g data-mml-node="mo" transform="translate(2473.4, 0)"> <use xlink:href="#MJX-4-TEX-N-28"> </use> </g> <g data-mml-node="mn" transform="translate(2862.4, 0)"> <use xlink:href="#MJX-4-TEX-N-32"> </use> </g> <g data-mml-node="mo" transform="translate(3584.6, 0)"> <use xlink:href="#MJX-4-TEX-N-2212"> </use> </g> <g data-mml-node="mi" transform="translate(4584.8, 0)"> <use xlink:href="#MJX-4-TEX-I-6D"> </use> </g> <g data-mml-node="mo" transform="translate(5462.8, 0)"> <use xlink:href="#MJX-4-TEX-N-29"> </use> </g> <g data-mml-node="mi" transform="translate(5851.8, 0)"> <use xlink:href="#MJX-4-TEX-I-3C0"> </use> </g> <g data-mml-node="mo" transform="translate(6644.1, 0)"> <use xlink:href="#MJX-4-TEX-N-2B"> </use> </g> <g data-mml-node="mn" transform="translate(7644.3, 0)"> <use xlink:href="#MJX-4-TEX-N-32"> </use> </g> <g data-mml-node="mi" transform="translate(8144.3, 0)"> <use xlink:href="#MJX-4-TEX-I-6D"> </use> </g> <g data-mml-node="mo" transform="translate(9022.3, 0)"> <use xlink:href="#MJX-4-TEX-N-28"> </use> </g> <g data-mml-node="mo" transform="translate(9411.3, 0)"> <use xlink:href="#MJX-4-TEX-N-2212"> </use> </g> <g data-mml-node="mn" transform="translate(10189.3, 0)"> <use xlink:href="#MJX-4-TEX-N-31"> </use> </g> <g data-mml-node="msup" transform="translate(10689.3, 0)"> <g data-mml-node="mo"> <use xlink:href="#MJX-4-TEX-N-29"> </use> </g> <g data-mml-node="mi" transform="translate(389, 413) scale(0.707)"> <use xlink:href="#MJX-4-TEX-I-6D"> </use> </g> </g> <g data-mml-node="msup" transform="translate(11915.8, 0)"> <g data-mml-node="mi"> <use xlink:href="#MJX-4-TEX-N-73"> </use> <use xlink:href="#MJX-4-TEX-N-69" transform="translate(394, 0)"> </use> <use xlink:href="#MJX-4-TEX-N-6E" transform="translate(672, 0)"> </use> </g> <g data-mml-node="TeXAtom" transform="translate(1228, 413) scale(0.707)"> <g data-mml-node="mo"> <use xlink:href="#MJX-4-TEX-N-2212"> </use> </g> <g data-mml-node="mn" transform="translate(778, 0)"> <use xlink:href="#MJX-4-TEX-N-31"> </use> </g> </g> </g> <g data-mml-node="mo" transform="translate(14097.5, 0)"> <use xlink:href="#MJX-4-TEX-N-2061"> </use> </g> <g data-mml-node="mrow" transform="translate(14097.5, 0)"> <g data-mml-node="mo"> <use xlink:href="#MJX-4-TEX-S3-28"> </use> </g> <g data-mml-node="mfrac" transform="translate(736, 0)"> <g data-mml-node="mrow" transform="translate(220, 676)"> <g data-mml-node="mi"> <use xlink:href="#MJX-4-TEX-N-73"> </use> <use xlink:href="#MJX-4-TEX-N-69" transform="translate(394, 0)"> </use> <use xlink:href="#MJX-4-TEX-N-6E" transform="translate(672, 0)"> </use> </g> <g data-mml-node="mo" transform="translate(1228, 0)"> <use xlink:href="#MJX-4-TEX-N-2061"> </use> </g> <g data-mml-node="TeXAtom" transform="translate(1394.7, 0)"> <g data-mml-node="mi"> <use xlink:href="#MJX-4-TEX-I-69"> </use> </g> </g> </g> <g data-mml-node="mi" transform="translate(789.8, -686)"> <use xlink:href="#MJX-4-TEX-I-6E"> </use> </g> <rect width="1939.7" height="60" x="120" y="220"> </rect> </g> <g data-mml-node="mo" transform="translate(2915.7, 0)"> <use xlink:href="#MJX-4-TEX-S3-29"> </use> </g> </g> <g data-mml-node="mo" transform="translate(17971.4, 0)"> <use xlink:href="#MJX-4-TEX-N-2212"> </use> </g> <g data-mml-node="mn" transform="translate(18971.6, 0)"> <use xlink:href="#MJX-4-TEX-N-32"> </use> </g> <g data-mml-node="mo" transform="translate(19471.6, 0)"> <use xlink:href="#MJX-4-TEX-N-28"> </use> </g> <g data-mml-node="mo" transform="translate(19860.6, 0)"> <use xlink:href="#MJX-4-TEX-N-2212"> </use> </g> <g data-mml-node="mn" transform="translate(20638.6, 0)"> <use xlink:href="#MJX-4-TEX-N-31"> </use> </g> <g data-mml-node="msup" transform="translate(21138.6, 0)"> <g data-mml-node="mo"> <use xlink:href="#MJX-4-TEX-N-29"> </use> </g> <g data-mml-node="mi" transform="translate(389, 413) scale(0.707)"> <use xlink:href="#MJX-4-TEX-I-6D"> </use> </g> </g> <g data-mml-node="mi" transform="translate(22198.4, 0)"> <use xlink:href="#MJX-4-TEX-I-69"> </use> </g> </g> </g> </svg> Note that what appears as letters and symbols are actually curves. You could probably save time by using a font that uses these Unicode characters, for example Times News Roman. There is still one difficulty, fractions. Here I have used a line repeated as many times as necessary, then put a text box for the numerator and then for the denominator. modified formula.afdesign

Hello everyone, When you type an ASCII apostrophe U+0027 (') in a text box in Affinity Publisher, it automatically changes to a typographical apostrophe U+2019 (’), which is often a good thing. However, this is not the case in the search input cell. For example, if you have written a text about Alice’s Restaurant and you search for occurrences by typing the sequence Alice's Restaurant in the search bar, you will not find it. Just as upper and lower case letters are not differentiated by the search, the 3 kinds of apostrophes should not be differentiated, unless a specific option is checked in the search, and the same for the 18 kinds of spaces, and the 14 kinds of quotes.

v. 2.0.3.1688 Hello to all, When you copy a word (double click the mouse), when you paste the copied word in the search bar, it is pasted with a space in front or behind. This naturally leads to errors when it comes to searching for all occurrences of a word. copy-space.mp4

After much procrastination, and a lot of back and forth, I have just received a conclusive answer from the company. It is the company Amazon. Thank you for your patience. We have reproduced the problem and found that your file contains problems with the transparencies/layers, which cause the file to fail during the upload process. The transparencies/layers cause conversion errors and manufacturing errors at the time of printing. In order to fix the file, you will need to pixelate groups of vectors into single images or the entire page into a single image. When editing your inner file, you will need to flatten all transparencies. During processing, the transparencies are flattened and may cause corrupted data or conversion errors in the process. Once you have revised your file, you will need to create a new PDF, ensuring that all transparencies are fully flattened. This should be a new file, with a new name, and you should not use the automatic setting, but it is also set for the trim size. When creating a new PDF, we recommend that you use the Print to PDF section of the following resource: To solve this problem, we recommend that you convert your file using the ‘Print to PDF’ option. This will flatten any transparencies or layers in the file. The ideal PDF format is PDF/X. Here are the PDF settings: Their answer does not hold water. My tests show that it is rather a surprising mismanagement of the Amazon server software. It is indeed pages 8 and 9 of the Affinity Publisher file that cause them problems. I have created an AFDESIGN map with the left part on page 8 and the right part on page 9. ♦️The initial AFPUBLISHER file (PDF 155 MB) was crashing on Amazon when checked even though it was well under 650 MB (Amazon's upload limit), as in this version the map was provided in vector format on both pages. 🟢The AFPUBLISHER file with only page 8 replaced by its PNG raster version (PDF 72 MB) is accepted without problems. 🟢The AFPUBLISHER file with only page 9 replaced by its PNG raster version (PDF 105 MB) is accepted without problems. 🟢The AFPUBLISHER file with both 8 and 9 replaced by their PNG raster version (PDF 22 MB) is accepted without problems. 🔴The original AFPUBLISHER version (the one that crashed with the two pages in vector format) gives in flatten PDF export a file of 668 MB. It seems to me that the Amazon server software interprets the PDF according to an old version of the PDF. PDF/X is based on PDF versions 1.3 to 1.6, but either the reprocessed file exceeds the 650 MB limit or produces a poor visual result.

This is what I was afraid of in the first question. A lot of time is lost if you have to go back to each index mark to automatically assign a character style to the words or phrases in the index marks. In this kind of work, we are often talking about thousands of marks. As an example, for a small book of 250 pages, pointing out each word or expression to add a style represents at the very least an unnecessary waste of time of about 10 to 12 hours of work that could be avoided. A feature should therefore be created to automatically assign a character style to words or phrases in index marks. For the second point, I haven't actually found how to change this once the entry mark has been entered.

Hello to all. I would like all indexed words to appear in the text with a particular font style. How do I do this effectively? What is the Override Style when inserting an index mark? Thank you for your explanations.