Re: Inode number and file size problems in version 3.2.1
On 7/1/2021 12:21 PM, Ken Brown via Cygwin wrote: On 7/1/2021 8:15 AM, Ruurd Beerstra via Cygwin wrote: [...] I found a patch (cygwin1-20210426.dll) with an updated cygwin1.dll. That fixed the hangs. [...] Note the wrong (changing) times when I use the current 'stat' (the first output is not the same as the 2nd one), while the old version consistently reports correct times, size and inode number. A quick test shows that the 'ls' command (I assume caused by the underlying stat(2) call) reports the same inode number for ALL files. It also reports either a size of "0" or 8192 for ALL files. Can you tell us something about i:\ivt so that someone could try to reproduce the problem? What kind of drive is i:? Does the path "i:\ivt" by any chance involve native symlinks or junctions? Ping? Can you answer the questions? If there's a bug in the 20210426 snapshot, we'd like to fix it. But first it would be good if you would test the most recent snapshot (20210507), available at https://cygwin.com/snapshots/, to see if it's already been fixed. Thanks. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] texinfo 6.8
The following packages have been uploaded to the Cygwin distribution: * texinfo-6.8-1 * texinfo-tex-6.8-1 * info-6.8-1 Texinfo is a documentation system that uses a single source file to produce output in a number of formats, both online and printed (dvi, html, info, pdf, xml, etc.). This is an update to the latest upstream release. See https://lists.gnu.org/archive/html/bug-texinfo/2021-07/msg00011.html for a list of changes since the previous release. Cygwin packaging The info package contains the standalone info viewer as well as the install-info program. The texinfo package contains everything else except support for the printable output formats (such as pdf). The texinfo-tex package supplies the latter. In particular, /usr/bin/makeinfo is in the texinfo package, but the command 'makeinfo --pdf' won't work unless you install texinfo-tex. Ken Brown Cygwin's texinfo maintainer -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
texinfo 6.8
The following packages have been uploaded to the Cygwin distribution: * texinfo-6.8-1 * texinfo-tex-6.8-1 * info-6.8-1 Texinfo is a documentation system that uses a single source file to produce output in a number of formats, both online and printed (dvi, html, info, pdf, xml, etc.). This is an update to the latest upstream release. See https://lists.gnu.org/archive/html/bug-texinfo/2021-07/msg00011.html for a list of changes since the previous release. Cygwin packaging The info package contains the standalone info viewer as well as the install-info program. The texinfo package contains everything else except support for the printable output formats (such as pdf). The texinfo-tex package supplies the latter. In particular, /usr/bin/makeinfo is in the texinfo package, but the command 'makeinfo --pdf' won't work unless you install texinfo-tex. Ken Brown Cygwin's texinfo maintainer
Re: [ANNOUNCEMENT] harfbuzz 2.8.1-1 (TEST)
On 5/20/2021 10:42 AM, Ken Brown via Cygwin-announce via Cygwin wrote: The following packages have been uploaded to the Cygwin distribution as test releases: * harfbuzz-2.8.1-1 * libharfbuzz0-2.8.1-1 * libharfbuzz-devel-2.8.1-1 * libharfbuzz-gobject0-2.8.1-1 * libharfbuzz-gobject-devel-2.8.1-1 * libharfbuzz-subset0-2.8.1-1 * libharfbuzz-subset-devel-2.8.1-1 * libharfbuzz-icu0-2.8.1-1 * libharfbuzz-icu-devel-2.8.1-1 * girepository-HarfBuzz0.0-2.8.1-1 These have now been promoted from test to current. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: getclip and putclip garble unicode characters
Replying to myself...
Mark Geisert wrote:
Hi Leonid (?),
Миронов Леонид Владимирович via Cygwin wrote:
getclip and putclip from cygutils-extra garble unicode characters: non-latin
characters copied to clipboard in windows are replaced with question marks when
retrieved with getclip in cygwin, and non-latin characters copied to clipboard
using putclip are pasted it in windows looking like utf-8 displayed in cp1252
but can be retrieved with getclip exactly as pasted, so it looks like the
problem is not in the way the data is copied but in the way cygwin and windows
communicate text encoding to each other. LC_CTYPE=en_US.UTF-8, windows ANSI
codepage is set to cp1251 - 1251, not 1252.
Thanks for the report. I will investigate.
I believe I have a local testcase similar to your report: If I select a region of
text on a message displayed from the Cygwin mailing list digest, and that message
has Cyrillic characters in it, getclip replaces those characters with '?' on output.
Since Thomas suggested an alternative, using 'cat < /dev/clipboard', I tried that
as well and see that here UTF-8 is output and the Cyrillic characters are intact.
So I've modified getclip to understand what MS calls CF_UNICODETEXT from the
clipboard and have it converted to UTF-8 for output. Thus my new getclip can
duplicate what the alternative does. (What getclip could understand previously
was CF_TEXT ("normal" ANSI characters) or CYGWIN_NATIVE (an internal Cygwin format
that makes your putclip + getclip example work)).
How about I generate a test version of the cygutils package with this updated
getclip and you can see if it solves your issue?
Stay tuned,
..mark
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
