<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Phil,<br>
<br>
thanks for testing and sharing your ideas!<br>
<br>
On 19.02.21 17:49, Philip Taylor wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Stefan Löffler wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f9243622-9683-00ae-b479-c3d079bf6904@gmail.com">
<pre wrap="">Dear TeXworks users,
a new minor release (0.6.6) is around the corner, which will hopefully
make it into TeXLive 2021. To get ready for that, I ask you to test the
latest version of TeXworks. It is available at the following (new!)
locations:
Windows: <a class="moz-txt-link-freetext" href="https://texworks.jfrog.io/artifactory/windows-latest/" moz-do-not-send="true">https://texworks.jfrog.io/artifactory/windows-latest/</a>
</pre>
</blockquote>
<br>
I <i>assumed</i> that the version offered for testing was
<a class="moz-txt-link-freetext"
href="https://texworks.jfrog.io/artifactory/windows-latest/0.7.0/TeXworks-win-0.7.0-202102181702-git_caae11d.zip"
moz-do-not-send="true">https://texworks.jfrog.io/artifactory/windows-latest/0.7.0/TeXworks-win-0.7.0-202102181702-git_caae11d.zip</a>,
but I would be grateful for clarification of this.</blockquote>
<br>
That looks correct.<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
Now installed, and will use it as my production TeXworks unless
something breaks, but I wonder if I might repeat some previous
requests and a previous bug report :<br>
</blockquote>
<br>
Absolutely. Please note, though, that at this stage I will likely
not add any new features (especially none that come with changes to
the user interface, which will then need translations, etc.).<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>[Bug] Attempting to save a new file as "Bundler.cover" with
"Save file as" set to "All files (*)" results in the file
being saved as "Bundler.cover.tex"; there appears no way to
save it as "Bundler.cover" as desired. </li>
</ul>
</blockquote>
<br>
Interesting. This works for me as expected on Linux. I'll have to
look into it on Windows.<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
</ul>
<ul>
<li>[Requested features] Support for draggable rulers</li>
</ul>
</blockquote>
<br>
As a feature request, this is not likely to happen before this
release. That being said, what do you mean by "draggable"? (I assume
you mean rulers in the PDF preview?)<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>Support for Ctrl +, Ctrl - & Ctrl 0 (zoom in, zoom out,
fit to screen). For that matter, Ctrl 1 (actual size) would
also be useful.</li>
</ul>
</blockquote>
<br>
I have all those (and more). Again, might be an OS thing (or
possibly a translation thing), but those functions are in the PDF
View menu and have the precise shortcuts you mention (except "fit to
screen", which probably translate to "fit to window", which for me
is Ctrl 3)<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li> The ability to open multiple source files in separate tabs
of a single window</li>
</ul>
</blockquote>
<br>
This has been on my wishlist for a long time, but unfortunately
requires some more internal restructuring first (which is on the
way, not not yet completed).<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>Add an "Open-as" option, within which the encoding can be
specified.</li>
</ul>
</blockquote>
<br>
This could be nice. My preferred method would be to auto-detect the
encoding if possible, however.<br>
Until that's done, you can open the document, select the desired
encoding in the status bar and then hit "reload using selected
encoding". I know it's a bit cumbersome (especially if you need to
use it a lot), but it should work.<br>
BTW: There is also a "magic comment" to define the encoding
[<a class="moz-txt-link-freetext" href="https://github.com/TeXworks/texworks/wiki/Magic-Comments">https://github.com/TeXworks/texworks/wiki/Magic-Comments</a>].<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>Could TeXworks be enhanced to (a) recognise, and (b) insert
if absent, a BOM in UTF-8 files ?</li>
</ul>
</blockquote>
<br>
It should be recognized, and you can toggle the insertion from the
status bar (clicking on the encoding should open a menu which has an
entry "write utf-8 byte order mark").<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>Would it be possible to augment TeXworks such that, no
matter in which window Ctrl-F/R is typed, it is interpreted in
the context of the source window rather than the preview
window ? As this would be a change to current behaviour, it
would have to be specified by a user preference or similar.
And for the rare occasion where one <i>does </i>want to
search (but not replace !) in the preview window, perhaps this
functionality could be exposed by Ctrl+Shft+F or similar.</li>
</ul>
</blockquote>
<br>
Hm, interesting idea, but I'd have to think about it.<br>
<br>
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>And/or — amend TeXworks to <i>not</i> steal focus from the
text-mode window when the PDF is displayed. A frequent usage
scenario is that one is performing a series of
search-and-replace experiments in the text-mode window while
observing the effect in the PDF window, and with the current
behaviour the next search is invariably a "Search PDF" rather
than a "Search text" as desired.</li>
</ul>
</blockquote>
<br>
You can (sort of) do that already. In the preferences under
Typesetting, select your tool, click "Edit..." and untick "View PDF
after running". The first time you tex a new document, you'd have to
open it manually (e.g. via "Window > Go to preview". Any other
time you open the tex, the pdf should still be opened automatically,
and TeXworks would not "steal" your focus.<br>
<br>
HTH,<br>
Stefan<i><br>
</i>
</body>
</html>