Jeremy Huntwork wrote these words on 04/11/06 09:23 CST:
Anyway, I went ahead and updated the ticket with the patch you sent in
this thread.
I initially had trouble getting this patch to work, and couldn't
figure out why. I worked a bit comparing the patch downloaded from
Trac, and the one
Randy McMurchy wrote:
Apparently, uploading patches to Trac causes a change in the line
ending characters (cr, lf chars). After downloading the patch from
Trac, and then applying it, there are messages about it having to
strip cr/lf chars from the patch. This doesn't happen applying the
one
On 4/12/06, Jeremy Huntwork [EMAIL PROTECTED] wrote:
Actually, this is probably wholly my fault, and not Trac. Yesterday I
did this on my work desktop, which is sadly, Windows. So I had
downloaded the patch Alexander sent to my Windows box and then uploaded
it from there. I know Windows likes
On Wed, Apr 12, 2006 at 10:59:42AM -0500, Bruce Dubbs wrote:
Do you have cygwin installed? If so, you could test this behavior.
BTW, this is a standard feature of a ftp transfer in ascii mode. Been
around for years before Windows.
Yes, I believe I have cygwin. What did you want me to do?
--
On Wed, Apr 12, 2006 at 10:59:42AM -0500, Bruce Dubbs wrote:
Do you have cygwin installed? If so, you could test this behavior.
BTW, this is a standard feature of a ftp transfer in ascii mode. Been
around for years before Windows.
Btw, here's how I had intendend to test this issue. My LFS
Jeremy Huntwork wrote:
On Wed, Apr 12, 2006 at 10:59:42AM -0500, Bruce Dubbs wrote:
Do you have cygwin installed? If so, you could test this behavior.
BTW, this is a standard feature of a ftp transfer in ascii mode. Been
around for years before Windows.
Yes, I believe I have cygwin. What
big enhansement for Peenis
http://www.500channelsfocus.com?iYeR-gfO.YbWPMeSVXRhSjQhc,VSd
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Dan Nicholson write:
Referencing ticket 1827
(http://wiki.linuxfromscratch.org/blfs/ticket/1827), I was hoping for
some review on a commit to put a link to Locale Related Issues for
Nano-1.2.5. On the Locale page, there's simply a link to the 1.3.11
tarball with the information that the build
Dan Nicholson wrote:
On 4/12/06, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Not really a suggestion, but I think that the whole idea of the locale related
issues page failed. The Wiki contains a lot of candidate information for this
page, and the process of its addition is too slow.
So
I'm testing this again now. Implementation seems incomplete.
On 4/5/06, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Dan Nicholson пишет:
Does this include the following?
1) the ability to view Russian translation of wrote at the top of this
message
The word comes out correctly, but
On 4/12/06, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Dan Nicholson wrote:
You're probably right about that. What does everyone think about
this? My thoughts are that pointing to the Wiki is good for stopgap
solutions like suggesting upgrading a version. However, if the book
was
Alexander E. Patrakov wrote:
Which of the following types of notes are considered stopgap solutions?
What's the proper place for each one in the released book (one of: the
main package page, Locale-Related Issues page, Wiki)?
I'm not completely up to speed on all of the locale issues. What
DJ Lucas wrote:
Lastly, while still on the locale issues page, I'm not qualified to
write the text, but I'd like to see some specific examples of the types
of problems that may be seen, along with a short paragraph or two about
the adoption of UTF-8 and it's use in other distro's as an example
13 matches
Mail list logo
