Re: Reminder: master branch is frozen for non-documentary changes
On 6/15/23, G. Branden Robinson wrote: > What do y'all think of this plan? There's been no public response, which typically means no one objects, but I'll go on record with a positive endorsement of the plan. Thanks for driving the new release!
Re: ms/mm page margins too large
What size is your actual page. It looks like you want A4. Thanks - Damian Pacific Engineering Systems International . 20D Grose St, Glebe NSW 2037 Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here Views & opinions here are mine and not those of any past or present employer
ms/mm page margins too large
Hello! I was trying to set up an ms-document with small page margins (see attachment), but I don't seem to get below a certain limit (especially on the bottom side). In one-column mode, the bottom border is a bit smaller, but still larger than 1cm. I also cannot explain the spacing introduced by the .2C request (between BEFORE and AFTER). Build with pdfroff -ms margins.ms >margins-ms.pdf Does anybody understand what's going on? I've tried something similar with mm (margins.mm), trying to set 1cm margins on all sides. This doesn't work as well when built with: pdfroff -mm -P-pa4 -rW=19c -rO=1c -rL=27.7c margins.mm >margins-mm.pdf Although, here we can at least set the page length to something oversized like 31c to get close to what we want. A4 has a height of 29.7cm, so this is also strange. For my particular task, I will probably just switch from ms to mm. But it would be nice to understand why they behave this way. Yours sincerely, Robin\# pdfroff -mm -P-pa4 -rW=19c -rO=1c -rL=27.7c margins.mm >margins.pdf .PGNH .SP 1c BEFORE .2C AFTER . .nr i 0 1 .while \n+i<=100 \{\ . br . nop \ni .\}\# pdfroff -ms margins.ms >margins.pdf .nr PO 1c .nr LL 21c-\n(PO-1c .nr HM 1c .\" FIXME: The actual bottom border is much larger. .nr FM 1c .nr PI 0 .\" Disable headers and footers .ds CH .ds CF . BEFORE .2C AFTER . .nr i 0 1 .while \n+i<=100 \{\ . br . nop \ni .\} margins-ms.pdf Description: Adobe PDF document margins-mm.pdf Description: Adobe PDF document
Re: PDF outline not capturing Cyrillic text
On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote: > Hello Peter, > > I am also now stumbling across Cyrillc-related issues with pdfmark. I am > using ms for the time being. The bug also affects autogenerating link texts > given via `.pdfhref L`. > In the most simple case, preconv will turn your Cyrillic characters into > escapes which are apparently not further interpreted by pdfmark (or > anything that follows). I see text like "[u0421][u043F]..." in my outline. > > I believe that this is why you have .pdfmomclean in MOM. Do I understand > correctly that this is supposed to turn the escapes back into Latin-1? > This is presumably mainly the work of .asciify, which would be misnamed > anyway. It does not work with Cyrillic at all, which doesn't surprise. > That's also why you don't get "mojibake garbage" in the outline. None of the > Cyrillic characters end up in intermediate output. > > It also explains why I previously had no problems with German Unicode > characters (that was using MOM) - they can be converted back into Latin-1. > > Manually editing the ps:exec lines in the intermediate output and inserting > Unicode characters there, does not produce the desired results, which is > also not surprising. > > So it seems that the main problem really lies in grops and/or gropdf which > should ideally work with the Unicode escapes produced by preconv. > I am not sure if we would still need .pdfmomclean. But whatever useful stuff > it currently does, it should probably be in pdfmark.tmac (and/or pdf.tmac?) > instead. > > Best regards, > Robin Hi Robin, The features you require are coming. This is an example of Russian with bookmarks in cyrillic. I'm afraid I don't know what it means and I have forgotten where I got the text. Cheers Deri Rus2.pdf Description: Adobe PDF document
Re: PDF outline not capturing Cyrillic text
Hello Peter, I am also now stumbling across Cyrillc-related issues with pdfmark. I am using ms for the time being. The bug also affects autogenerating link texts given via `.pdfhref L`. In the most simple case, preconv will turn your Cyrillic characters into escapes which are apparently not further interpreted by pdfmark (or anything that follows). I see text like "[u0421][u043F]..." in my outline. I believe that this is why you have .pdfmomclean in MOM. Do I understand correctly that this is supposed to turn the escapes back into Latin-1? This is presumably mainly the work of .asciify, which would be misnamed anyway. It does not work with Cyrillic at all, which doesn't surprise. That's also why you don't get "mojibake garbage" in the outline. None of the Cyrillic characters end up in intermediate output. It also explains why I previously had no problems with German Unicode characters (that was using MOM) - they can be converted back into Latin-1. Manually editing the ps:exec lines in the intermediate output and inserting Unicode characters there, does not produce the desired results, which is also not surprising. So it seems that the main problem really lies in grops and/or gropdf which should ideally work with the Unicode escapes produced by preconv. I am not sure if we would still need .pdfmomclean. But whatever useful stuff it currently does, it should probably be in pdfmark.tmac (and/or pdf.tmac?) instead. Best regards, Robin