Re: Committed files with wrong charset

[Denis Barbier]

On Thu, Sep 02, 2004 at 11:02:41PM +0300, Tommi Vainikainen wrote:
> I accidentally committed two files, finnish/ports/index.wml and
> finnish/ports/freebsd/index.wml, with charset problems. Latter one was
> UTF-8 encoded, but should be ISO-8859-15. First one had some strange
> Emacs chars.
> 
> My problem is that
> 
> ...ports/freebsd$ cvs diff index.wml
> ...ports/freebsd$ recode utf8..latin9 index.wml
> ...ports/freebsd$ cvs diff index.wml
> 
> So, cvs doesn't detect any changes after recoding file to correct
> charset. Therefore I cannnot commit correct version. What should I do?
> Remove file and add again?

That's weird.
A simpler solution is add an empty line at the end of your file.

Denis

Committed files with wrong charset

[Tommi Vainikainen]

I accidentally committed two files, finnish/ports/index.wml and
finnish/ports/freebsd/index.wml, with charset problems. Latter one was
UTF-8 encoded, but should be ISO-8859-15. First one had some strange
Emacs chars.

My problem is that

...ports/freebsd$ cvs diff index.wml
...ports/freebsd$ recode utf8..latin9 index.wml
...ports/freebsd$ cvs diff index.wml

So, cvs doesn't detect any changes after recoding file to correct
charset. Therefore I cannnot commit correct version. What should I do?
Remove file and add again?

-- 
Tommi Vainikainen

Your Subscription Request Response

[Focalex]

This message is an automated response.  You are receiving this email because 
you replied to the confirmation email we sent you in response to your Focalex 
subscription request.

  The confirmation email has the following subject.
   "Important! Your confirmation is needed!"

As stated in the email, replying to the message does nothing.  You must use
the links contained in the confirmation email if you subscribed within the past
30 days (subscription requests expire after 30 days).

If you are currently receiving emails from Focalex and wish to unsubscribe,
simply use the "Manage Your Subscriptions" link contained at the top of every
email Focalex sends to its subscribers.

If you have any further questions, you may contact us at:
[EMAIL PROTECTED]

Cheers!
The Focalex Team

Re: Some spelling corrections

[doug jensen]

On Thu, Sep 02, 2004 at 10:59:03AM +0200, Florian Ernst wrote:
> Thanks for your suggestions (even though you don't comment on anything
> introduced in my patch, but only on issues not touched by me) :)

Oh darn it all, I've missed the point of the thread again :)

> 
> On Wed, Sep 01, 2004 at 10:30:57PM -0600, doug jensen wrote:
> > Being familiar with the Unix environment (and specially GNU userland, found 
> > in
> > s/specially/especially
> 
> There are 39 uses of [Ss]pecially in the English pages, so I rather
> leave this for others.

It is especially difficult for me to explain the difference, maybe an
example sentence will help.
  The computer was specially made with high quality components, but she
  especially liked the Debian GNU/Linux operating system.
The 'especially' points out a specific part or function, within a group
or collection.  Or intensifies a point, that is, it has been especially
nice discussing this with you.


-- 
Doug Jensen

Bug#269591: No list archive for september 2004 on debian-devel mailing list page

[Erik Schanze]

Package: www.debian.org
Severity: normal

Hi!

There is no "Sep" link for archived mails of debian-devel mailing list
on page http://lists.debian.org/debian-devel/

The september 2004 is 2 days old and some mails were send to debian-devel,
but are not available in archive.


Regards,
Erik


-- 
 www.ErikSchanze.de *
 Bitte keine HTML-Mails! No HTML mails, please! Maillimit: 1 MB *
  * Linux-Info-Tag in Dresden, am 30. Oktober 2004  *
 Info: http://www.linux-info-tag.de *

【アンケートご協力のお願い】

[ASSET NAVI 事務局]

　┏━━━┓
　　　■　ASSET BIKE アンケートのお願い　■
　　ライダーのバイク環境をよくする
ライダーズアンケートにご協力ください。
　　　http://www.asset819.net/
　┗━━━┛
　突然のメールで大変失礼致します。

　とかく肩身の狭い思いをするライダーの環境を安全安心の環境にするため、
　現在アンケート調査を実施しております。ぜひご協力お願いできないかと思い、
　メールをお送りいたしました。

　弊社は地元バイク店を中心としたライダーとショップのための
　バイク情報サイトを展開しております。

http://www.asset819.net/


ぜひライダーの環境をよくするため、また、今後のサービスをより向上させるため
ライダーアンケートにご協力お願いいたします。

　　　=＝　
　　　もしバイクに乗っていらっしゃらない、または、全く興味がなければ、
　　　ぜひお友達のライダーの方へこのライダーアンケートをご紹介いただけ
　　　ないでしょうか
　　　＝＝===

◆非常に簡単なアンケートで、2、3分で終えられます。
◆バイク店についてのご質問ですので、どう思っているか素直な感想で結構です。
◆個人情報は口外することはございませんのでご安心ください。

　-
　あなた様のご意見は極めて重要です。
　あなた様を含めた100名様のご意見を元に、今後のショップ側でのシステム展開、
　サービス展開が決定するからです。
　-

お忙しいところ誠に恐縮ですが、貴重なお時間を数分いただき、アンケートに
ご協力ください。
　　
　　　◆アンケートフォーム
　　　⇒　http://www.asset-navi.com/anketo.html
　　　◆アセットナビHP
　　　⇒　http://www.asset819.net/
　　

  自分もバイクに乗っいていろんな経験をしてきました。
  実際乗っていてバイクに関わる環境、バイク業界、などに色々思うところがあり、
  本当の意味で新しいバイク文化を花咲かせたいと思い、サイトを立ち上げました。
  一人一人の声は私自身も含め小さいかもしれませんが、みんなが集まれば大きな
  武器になると考えており、今後も次々に新しい企画を考え、バイク業界に投げかけ
  ていきたいと思っております。
  第一弾として、「週刊、この店これっきり1台」という企画を近日公開予定です。



★お知り合いでライダーがいらっしゃいましたら、このアンケートにご協力いただ
　けないかご紹介ください。


よろしくお願いいたします。


もしご迷惑でしたら下記メールアドレスまで、返送お願いいたします。
今後メールが送信されないよう致します
┌┐
　　　ASSET BIKE 編集局
　HP http://www.asset819.net/
　mail [EMAIL PROTECTED]
Asset819システムはアセットナビのビジネスモデル特許（申請済み）
　
　　Copyright(C)asset navi Inc. 発行元：asset navi Inc.
└┘

Re: Some spelling corrections

[Florian Ernst]

Hello!

On Thu, Sep 02, 2004 at 10:46:01AM +0100, Adam D. Barratt wrote:
> Florian Ernst wrote, Thursday, September 02, 2004 9:59 AM
> > There are 39 uses of [Ss]pecially in the English pages, so I rather
> > leave this for others.
> 
> That one should be especially.

Thanks, changed.

> [...]
> >> message might overflow a buffer and which could result into executing
> arbitrary
> >> s/into/in
> 
> Definitely "...could result in...". "into" makes no sense in this context.
> In fact, the sentence makes no sense. :-)
> 
> It should be:
> 
> -message might overflow a buffer and which could result into executing
> arbitraty
> +message might overflow a buffer, which could result in executing arbitrary

Also changed, thanks.

Cheers,
Flo


signature.asc
Description: Digital signature

Re: Some spelling corrections

[Adam D. Barratt]

Florian Ernst wrote, Thursday, September 02, 2004 9:59 AM
[...]
> On Wed, Sep 01, 2004 at 10:30:57PM -0600, doug jensen wrote:
[...]
>> Being familiar with the Unix environment (and specially GNU userland,
found in
>> s/specially/especially
>
> There are 39 uses of [Ss]pecially in the English pages, so I rather
> leave this for others.

That one should be especially.

[...]
>> message might overflow a buffer and which could result into executing
arbitrary
>> s/into/in
>
> I'm not sure, but my dictionary agrees. "into" sounds good to me,
> though...

Definitely "...could result in...". "into" makes no sense in this context.
In fact, the sentence makes no sense. :-)

It should be:

-message might overflow a buffer and which could result into executing
arbitraty
+message might overflow a buffer, which could result in executing arbitrary

Regards,

Adam

Re: Some spelling corrections

[Florian Ernst]

Hello!

Thanks for your suggestions (even though you don't comment on anything
introduced in my patch, but only on issues not touched by me) :)

On Wed, Sep 01, 2004 at 10:30:57PM -0600, doug jensen wrote:
> manpage.  The proposal states more explicitly that the lack of a manpage is a
> # My understanding is that 'manpage' should be 'man page' however, I don't
> # know if it is worth changing all/any of them.

This issue isn't touched at all in this patch, all instances are left
as is for the moment.

> that library and breaks net installs until the dependent modules are rebuild.
> s/rebuild/rebuilt

Added, thanks.

> Being familiar with the Unix environment (and specially GNU userland, found in
> s/specially/especially

There are 39 uses of [Ss]pecially in the English pages, so I rather
leave this for others.

> also contains more upstream bugfixes wrt. dots in hostnames and unproper HTML
> s/wrt./regarding

This change is rather in style than in spelling. I think "wrt." might
stay...

> s/unproper/improper

Added, thanks.

> message might overflow a buffer and which could result into executing 
> arbitrary
> s/into/in

I'm not sure, but my dictionary agrees. "into" sounds good to me,
though...

An updated patch can be found here:
 (161K)
or here:
 (41K)


OK, if this patch won't find further review, here is how I'm going to
proceed:
I will commit these changes one after another (against my original
intentions), also bumping the translation-check header of all
corresponding translation in the process. Or are there any sections
where people frown upon foreign commits in their territory?
All unclear parts that will be left thereafter will be posted again as
a (hopefully) smaller patch.


Cheers,
Flo


signature.asc
Description: Digital signature