Re: Using Comment notes the right way
On 2023-11-21 18:19, Richard Kimberly Heck wrote: On 11/21/23 06:17, Jean-Marc Lasgouttes wrote: Le 21/11/2023 à 07:54, Daniel a écrit : I see. But my point was that I don't think that it is specific to my use case. The reason being that the comment feature is a default feature found in many applications these days and that this indicates a quite general usefulness of it. As I wrote before, the main feature that would make me like a new comment inset would be to be able to show the name and color of the user who entered it when some in change tracking mode. As Isaac said, the todonotes module provides notes with this kind of functionality. I guess the original idea was to do that automatically rather than having to do it manually which is quite cumbersome. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Translations for LyX 2.4
On 11/19/23 05:56, madmurphy wrote: Hi! First of all congratulations for the good work! Any chances the hereapplies module* will be included with this release? * https://github.com/madmurphy/hereapplies.sty/tree/main/lyx-module Could you explain what this does? Also, the module would need updating to most recent format. (You can just use the layout2layout.py script to do that.) Also, it seems that the two inset types are each defined twice. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
I am so sorry, I tried it again and I can no longer reproduce either :-( I will try to think of if there was anything I was doing differently earlier. On Tue, Nov 21, 2023, at 5:08 PM, Pavel Sanda wrote: > On Tue, Nov 21, 2023 at 10:26:06AM -0500, Alexander Dunlap wrote: > > I tried the same PDF in all three scenarios. > > Ok, you challenged me to test this on both TL 2022 (debian based) and TL 2023 > (installed locally for a standalone user). > Everything worked in both TL 2022 & 2023. > > Could you give me exact recipy how to reproduce your problem? > Perhaps something specific about the pdf itself (you can send it to me > privately if it's not conbfidental). > > Thanks, > Pavel > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
On Tue, Nov 21, 2023 at 10:26:06AM -0500, Alexander Dunlap wrote: > I tried the same PDF in all three scenarios. Ok, you challenged me to test this on both TL 2022 (debian based) and TL 2023 (installed locally for a standalone user). Everything worked in both TL 2022 & 2023. Could you give me exact recipy how to reproduce your problem? Perhaps something specific about the pdf itself (you can send it to me privately if it's not conbfidental). Thanks, Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Using Comment notes the right way
On 11/21/23 02:29, Isaac Oscar Gariano wrote: The `todonotes` module provides insets for this... Personally though I just defined my own inset... Right! This is the "LyX way": Leverage the gazillion packages that already exist, or else define your own. Also I'd have some of the modules be loaded by default, such as the todonotes module, and title and preamble hacks. That you can do: Just create a blank document, load these modules, and click "Save As Document Defaults" in Document> Settings. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Using Comment notes the right way
On 11/21/23 06:17, Jean-Marc Lasgouttes wrote: Le 21/11/2023 à 07:54, Daniel a écrit : I see. But my point was that I don't think that it is specific to my use case. The reason being that the comment feature is a default feature found in many applications these days and that this indicates a quite general usefulness of it. As I wrote before, the main feature that would make me like a new comment inset would be to be able to show the name and color of the user who entered it when some in change tracking mode. As Isaac said, the todonotes module provides notes with this kind of functionality. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
I tried the same PDF in all three scenarios. On Tue, Nov 21, 2023, at 10:06 AM, Pavel Sanda wrote: > On Tue, Nov 21, 2023 at 08:48:40AM -0500, Alexander Dunlap wrote: > > None of these tests give me any error messages. However, when I test it with > > the absolute path, the output I get is different. I ran it on a two-page PDF > > and with relative paths the resulting PDF is a single page with both pages > > side by side, in a file called ORIGINALFILENAME-sidebyside.pdf. However, > > when > > I run it with an absolute path, I get a PDF (in the same filename) with only > > the text "width=!,height=!,pages=-,nup=2x1" > > Thanks for your feedback. I do not see any problem here. > > One possibility is that pdflatex changed again in new TL version, > second option is that there is something specific about the pdf > which you tried with the absolute path. Or you tried the same > pdf in all three scenarios? > > Pavel > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
On Tue, Nov 21, 2023 at 08:48:40AM -0500, Alexander Dunlap wrote: > None of these tests give me any error messages. However, when I test it with > the absolute path, the output I get is different. I ran it on a two-page PDF > and with relative paths the resulting PDF is a single page with both pages > side by side, in a file called ORIGINALFILENAME-sidebyside.pdf. However, when > I run it with an absolute path, I get a PDF (in the same filename) with only > the text "width=!,height=!,pages=-,nup=2x1" Thanks for your feedback. I do not see any problem here. One possibility is that pdflatex changed again in new TL version, second option is that there is something specific about the pdf which you tried with the absolute path. Or you tried the same pdf in all three scenarios? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Using Comment notes the right way
On 2023-11-21 12:17, Jean-Marc Lasgouttes wrote: Le 21/11/2023 à 07:54, Daniel a écrit : I see. But my point was that I don't think that it is specific to my use case. The reason being that the comment feature is a default feature found in many applications these days and that this indicates a quite general usefulness of it. As I wrote before, the main feature that would make me like a new comment inset would be to be able to show the name and color of the user who entered it when some in change tracking mode. Having a comment feature that is linked to the change tracking machinery would be good. The issue of knowing how to typeset them, though, is not that easy. I am not sure which specificity of implementation you are after. But the pdfcomment package supports the "author=..." option for individual comments (as well as the "color=..." option). I also want to point out that Comment notes (mentionned in the subject of the thread) have nothing to do with that. These are just notes that are visible in the document source, but not typeset. This is in contrast with plain notes, that are not exported at all. This question of having this potentially private information present or not in the .tex file is more important IMO than having it visible to the end user. > Finally, my remark about "MSWord in a box" was undeserved, and I apologize for that. I should have fought a bit more the urge of making fun of the idea. However, if allowing free spacing in comments is considered a worthy feature (after all everybody else does that), then why not allow it everywhere then? Everybody has its own habits, after all, and I am sure some people would enjoy this. I think not allowing free spacing and empty lines in the main text is helpful because it indicates what is going on in the output. Double spaces and extra empty lines will be swallowed by LaTeX. The idea with comments was that since they are not typeset that way, it might make sense to allow for more freedom of how to enter stuff. So that seems to be an important difference. But I see now that things are not as easy as they seemed to me at first. Because one might see not being able to enter extra spaces and empty lines not only as related to the output but as help to avoid them in general. Maybe that is one of your concerns? If the pdfcomment package is used for output, I would highly recommend allowing for more freedom in spacing (something that the module lacks) since it only supports plain text as far as I can see. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
None of these tests give me any error messages. However, when I test it with
the absolute path, the output I get is different. I ran it on a two-page PDF
and with relative paths the resulting PDF is a single page with both pages side
by side, in a file called ORIGINALFILENAME-sidebyside.pdf. However, when I run
it with an absolute path, I get a PDF (in the same filename) with only the text
"width=!,height=!,pages=-,nup=2x1"
Alex
On Tue, Nov 21, 2023, at 6:00 AM, Pavel Sanda wrote:
> On Mon, Nov 20, 2023 at 10:34:48AM -0500, Alexander Dunlap wrote:
> > Yes that is right, sorry for not reading carefully. :-)
>
> Alas, the former fix breaks with path specifications.
>
> The path searching mechanism of pdflatex (when -output-directory is used)
> is willing to consider current directory for path like "../../a/b/file"
> but is unwilling to consider current directory when only "file" is provided.
> Weird.
>
> Alexander, would you mind testing for me 2nd version of the patch?
> You need to unwind the last patch ("-R" for patch or just delete the
> simple change manually) and then apply the current one.
>
> 3 scenarios to be tested:
> 1. a5toa4 local_file.pdf
> 2. a5toa4 some_relative_path/file.pdf
> 3. a5toa4 /absolute_path/file.odf
>
> Works here with TL 2020, but I worry what other changes on searching
> mechanisms of -output-directory awaits in the future TLs.
> Pavel
>
> --
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel
>
>
> *Attachments:*
> • pf2.patch
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Using Comment notes the right way
Le 21/11/2023 à 07:54, Daniel a écrit : I see. But my point was that I don't think that it is specific to my use case. The reason being that the comment feature is a default feature found in many applications these days and that this indicates a quite general usefulness of it. As I wrote before, the main feature that would make me like a new comment inset would be to be able to show the name and color of the user who entered it when some in change tracking mode. Having a comment feature that is linked to the change tracking machinery would be good. The issue of knowing how to typeset them, though, is not that easy. I also want to point out that Comment notes (mentionned in the subject of the thread) have nothing to do with that. These are just notes that are visible in the document source, but not typeset. This is in contrast with plain notes, that are not exported at all. This question of having this potentially private information present or not in the .tex file is more important IMO than having it visible to the end user. Finally, my remark about "MSWord in a box" was undeserved, and I apologize for that. I should have fought a bit more the urge of making fun of the idea. However, if allowing free spacing in comments is considered a worthy feature (after all everybody else does that), then why not allow it everywhere then? Everybody has its own habits, after all, and I am sure some people would enjoy this. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [Offtopic] a5toa4
On Mon, Nov 20, 2023 at 10:34:48AM -0500, Alexander Dunlap wrote:
> Yes that is right, sorry for not reading carefully. :-)
Alas, the former fix breaks with path specifications.
The path searching mechanism of pdflatex (when -output-directory is used)
is willing to consider current directory for path like "../../a/b/file"
but is unwilling to consider current directory when only "file" is provided.
Weird.
Alexander, would you mind testing for me 2nd version of the patch?
You need to unwind the last patch ("-R" for patch or just delete the
simple change manually) and then apply the current one.
3 scenarios to be tested:
1. a5toa4 local_file.pdf
2. a5toa4 some_relative_path/file.pdf
3. a5toa4 /absolute_path/file.odf
Works here with TL 2020, but I worry what other changes on searching
mechanisms of -output-directory awaits in the future TLs.
Pavel
--- pfarrei.tlu 2023-11-21 11:43:19.611137725 +0100
+++ pfarrei.tlu 2023-11-21 11:46:53.993277671 +0100
@@ -100,11 +100,15 @@
-- build the temporary tex file
local tmpdir = os.tmpdir("pfarrei.XX" )
local tmpfile = string.match( arg[i], '.*/(.*)$') or arg[i]
+ -- pdflatex's -output-directory search for source pdf works with path
specification but fails
+ -- when simple file name in the current working directory is provided,
we need to provide '../' then
+ local local_source=''
+ if tmpfile == arg[i] then local_source = '../' end
local basename = string.match( tmpfile,'(.*)%.[^.]*$') or tmpfile
tmpfile = tmpdir..'/'..basename..'.tex'
local file = assert( io.open( tmpfile, 'w' ) )
if booklet then assert(
file:write("\\PassOptionsToPackage{booklet}{pfarrei}\n") ) end
- assert( file:write("\\def\\OriginalFile{",arg[i],"}\n") )
+ assert( file:write("\\def\\OriginalFile{"..local_source,arg[i],"}\n") )
assert( file:write("\\input{a5toa4.tex}\n") )
assert( file:flush() )
file:close()
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
