I don't find the place where the charset is defined in 9.02 en.
Could somebody indicate it?
I mean in web pages, some characters are not correcly displayed; and they are not displayed in the bookmarks as well.
--
Laurent Jumet - Point de Chat, Liège, BELGIUM
KeyID: 0xCFAF704C
[Restore address to laurent.jumet for e-mail reply.]
Tools - Preferences - General. At the bottom of that dialogue box you can
set your 'preferred' language; click on 'Details' to get the dialogue box
where you can add or remove languages and change the order of preference
for web pages (and the language for your user interface and the
character-set to assume for pages that don't specify which one to use).
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
Could it be: View menu > Encoding > ?
> I don't find the place where the charset is defined in 9.02 en.
> Could somebody indicate it?
You can find the encoding (charset) information that Opera is using by
enabling the Info panel (Tools - Appearance - Panels - Info), and override
the encoding used on a specific page by going to the View - Encoding menu.
You can set the default fallback encoding in Tools - Preferences -
Language, but you should only do so if you know what you are doing, the
default should be ok for most people.
> I mean in web pages, some characters are not correcly displayed; and
> they are not displayed in the bookmarks as well.
Could you please give some examples of pages that are not displaying
properly for you? We do know they exist, but knowing specific cases makes
it easier to do something about it.
--
\\// Peter Karlsson, software engineer, Opera Software
The opinions expressed are my own, and not those of my employer.
Please reply only by follow-ups in the newsgroup.
Whiskers <catwh...@operamail.com> wrote:
>> I don't find the place where the charset is defined in 9.02 en.
>> Could somebody indicate it?
>> I mean in web pages, some characters are not correcly displayed; and
>> they are not displayed in the bookmarks as well.
> Tools - Preferences - General. At the bottom of that dialogue box you can
> set your 'preferred' language; click on 'Details' to get the dialogue box
> where you can add or remove languages and change the order of preference
> for web pages (and the language for your user interface and the
> character-set to assume for pages that don't specify which one to use).
Yes, but charsets are not correct in bookmarks.
I suppose that those statements are for incoming pages and mail when they don't have any charset, and I stamped iso-8859-15 as this is the most relevant charset for belgian/French pages.
I'm using the English version of Opera9.02
"Lee Harvey" <leeh...@grassyknoll.com> wrote:
This is, as far as I understand, to override the charset stamped on the page (or on the message); or in case the page (or the message) comes without charset, to override the default charset that I defined to iso-8859-15 in my country (French).
But I don't know how this matches the charset of the text *inside* Opera, like the Bookmarks.
> But I don't know how this matches the charset of the text
> *inside* Opera, like the Bookmarks.
I think that's a system setting, if you're talking about the dropdown
menus.
There's a Tools > Preferences > Advanced > Fonts > Interface panels, but
it seems to be doing screwy things with the fonts for me right now -- I
probably need to restart Opera.
--
Ted <fedya at bestweb dot net>
TV Announcer: It's 11:00. Do you know where your children are?
Homer: I told you last night, *no*!
<http://www.snpp.com/episodes/4F06.html>
What 'User interface language' have you chosen in Tools - Preferences -
General' in the dialogue box that you get when you click on 'Details' next
to the drop-down box where you can select your 'preferred language'? I
have "/usr/share/opera//locale/english.lng" (I use Linux; the notation
will be different for Windows systems, and so might the options available).
The Opera 'Help' under "General Preferences" mentions "If you have
downloaded an Opera language file separately, go to the "Details" dialog to
apply it" but I can't find out where such files can be downloaded from.
Searching the Opera Knowledge Base did throw up this possibility (for
Windows systems):
http://www.opera.com/support/search/supsearch.dml?index=832> "No text
visible in user interface after upgrading to Opera 9" which suggests,
among other things, deleting the Opera 'locale' folder and then running the
Opera installation program again with the "Repair" option. Presumably that
means that Opera should be able to pick up the correct 'local language'
settings from your operating system and install the appropriate files for
its own interface.
You also have to make sure that the 'fonts' used by Opera include all the
symbols needed for the languages you are interested in.
The newsgroup opera.francais may have helpful information or people.
Whiskers <catwh...@operamail.com> wrote:
>> Yes, but charsets are not correct in bookmarks.
>> I suppose that those statements are for incoming pages and mail when
>> they don't have any charset, and I stamped iso-8859-15 as this is the most
>> relevant charset for belgian/French pages.
>> I'm using the English version of Opera9.02
> What 'User interface language' have you chosen in Tools - Preferences -
> General' in the dialogue box that you get when you click on 'Details' next
> to the drop-down box where you can select your 'preferred language'? I
> have "/usr/share/opera//locale/english.lng" (I use Linux; the notation
> will be different for Windows systems, and so might the options available).
I have just as you, english.lng
> The Opera 'Help' under "General Preferences" mentions "If you have
> downloaded an Opera language file separately, go to the "Details" dialog to
> apply it" but I can't find out where such files can be downloaded from.
I'm used with the English version of Opera.
Web pages are
French
Spanish
English
Default encoding for lacking Charset is iso-8859-15
But I don't have problems with the pages, only with text ascii>128 inside Opera (bookmarks).
This is not really a big problem.
snip
My copy of that file starts with this:
.-----
| ; Opera language file version 2.0
| ; Copyright 1995-2006 Opera Software ASA. All rights reserved.
| ; Created on 2006-09-19 14:04
| ; Lines starting with ; (like this) are comments and need not be translated
|
| [Info]
| Language="en"
| ; The string below is the language name in its own language
| LanguageName="English"
| Charset="iso-8859-1"
| Build.Linux=434
| Version.Linux=9.02
| DB.version=839
|
| [...]
'-----
Notice the Charset="iso-8859-1" in there. I imagine that if you need
characters not in that character set, then you need to specify a different
one in that file.
If you are happy with the rest of that file (ie everything in your user
interface being diplayed in English) then simply editing the file may be
all that is needed. Do this while Opera is not running. I suggest copying
the existing file into the same folder with a different name, such as
laurent.lng, and editing that; then you can select the new file from
Opera's 'Language' dialogue.
The bookmarks themselves are kept in a file called opera6.adr, which on my
system contains a line specifying utf8 encoding.
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
Whiskers <catwh...@operamail.com> wrote:
> My copy of that file starts with this:
>| Charset="iso-8859-1"
...mine too, and I changed it to Charset="iso-8859-15" to get the € (EUR) sign.
> The bookmarks themselves are kept in a file called opera6.adr, which on my
> system contains a line specifying utf8 encoding.
...this is very relevant.
Here must be the problem.
I've "UTF-8" too but may be it wasn't so in previous versions.
BTW: opening english.lng made me think to truncate "Enable cookies" to "Ck", and earn one centimeter on my task bar as I dragged the "Enable cookies" there.
This is an aside, but is there any way for you to set the line-length of
your articles to the usual 'less than 80 characters'? (75 is a good
setting, to allow for one or two levels of 'quoting' in replies).
Whiskers <catwh...@operamail.com> wrote:
>>> My copy of that file starts with this:
>>
>>>| Charset="iso-8859-1"
>>
>> ...mine too, and I changed it to Charset="iso-8859-15" to get the ?
>> (EUR) sign.
>>
>>> The bookmarks themselves are kept in a file called opera6.adr, which on
>>> my system contains a line specifying utf8 encoding.
>>
>> ...this is very relevant.
>> Here must be the problem.
>> I've "UTF-8" too but may be it wasn't so in previous versions.
>>
>>
>> BTW: opening english.lng made me think to truncate "Enable cookies" to
>> "Ck", and earn one centimeter on my task bar as I dragged the "Enable
>> cookies" there.
> This is an aside, but is there any way for you to set the line-length of
> your articles to the usual 'less than 80 characters'? (75 is a good
> setting, to allow for one or two levels of 'quoting' in replies).
On my editor, quotes are wrapped too, as you can see above.
Usually, people prefer no line limitation, as they are using different Fonts size.
Are you writing with OperaNews? If yes, this could be a feature request.
It is about NNTP and the RFC specified line length...
> Are you writing with OperaNews? If yes, this could be a
> feature request.
>
--
Opera Win32 9.02-8585; W2K
For Windows I suggest using the "classic" installer package in all
cases where feasible. </opinion>
snip
>> This is an aside, but is there any way for you to set the line-length of
>> your articles to the usual 'less than 80 characters'? (75 is a good
>> setting, to allow for one or two levels of 'quoting' in replies).
>
> On my editor, quotes are wrapped too, as you can see above.
> Usually, people prefer no line limitation, as they are using
> different Fonts size.
It is not easy to read a line of text that goes off the edge of the
display. A maximum line length of 80 characters has long been considered
the 'standard' for computer communications - being the width of a normal
display, on systems with no 'graphics' (and without using 'compressed' text
to squeeze more in).
It is 'good nettiquette' to make newsgroup articles (and emails) easily
readable by all users, no matter what equipment or software they may be
using. Remember that old machimes are still in use, and that not everyone
has the latest software or good eyesight. Here is the usual guideline for
"Writing Style on Usenet": <http://www.plig.net/nnq/ncaps.html> - see also
the newsgroup news.newusers.questions.
> Are you writing with OperaNews? If yes, this could be a feature request.
Opera is perfectly capable of sending newsgroup articles with a sensible
maximum line length. It can also read them perfectly well. Being a
graphical web browser it can also cope well with at least some articles
that ignore the usual 'best practice' (and can send messages that ignore
some of the 'best practice too).
I'm not using Opera to read and post in newsgroups; I use slrn, one of the
fastest and most powerful tools for the job.
I'm not familiar with the GoldED+ that you seem to be using. Looking at
<http://sourceforge.net/docman/display_doc.php?docid=939&group_id=2942> I
see that there is no obvious direct way to set a maximum line length for
the text which you write yourself using the internal editor; this seems an
odd omission. Is that line length set by the DISPMARGIN parameter in the
'message reader' section of the config?
I notice that there is a TEMPLATE NEWS.TPL "Newsgroups template" 7:1/*
> I'm not using Opera to read and post in newsgroups; I use slrn, one of
> the fastest and most powerful tools for the job.
A pity both GoldED and slrn don't support format=flowed :-)
--
Rijk
Opera Software ASA
QA etc
> Op Thu, 12 Oct 2006 20:22:39 +0200 schreef Whiskers
> <catwh...@operamail.com>:
>
>> I'm not using Opera to read and post in newsgroups; I use slrn,
>> one of
>
>> the fastest and most powerful tools for the job.
>
> A pity both GoldED and slrn don't support format=flowed :-)
The point is that the poster should observe and post correctly for
the medium. Only the poster can store a message on the server in
line-breaks-at-72-characters (or whatever). Most News Readers on the
other hand have local options to "wrap long lines". The onus is on
the poster here and in all cases IMHO.
A minority-adopted email format in newsgroups? <G>
.-----<http://joeclark.org/ffaq.html>
| [...]
| Whose brilliant idea was it, anyway?
| A posse of engineers at Eudora, spearheaded by Randy Gellens.
|
| What programs support f=f?
| Eudora 4.2 and later
| Microsoft Hotmail
| Mozilla Mail
| M2 (the Opera mail program)
| Apple Mail
|
| [...]
'-----
.-----<http://www.ietf.org/rfc/rfc2646.txt>
| 4.1. Generating Format=Flowed
|
| When generating Format=Flowed text, lines SHOULD be shorter than 80
| characters. As suggested values, any paragraph longer than 79
| characters in total length could be wrapped using lines of 72 or
| fewer characters. While the specific line length used is a matter of
| aesthetics and preference, longer lines are more likely to require
| rewrapping and to encounter difficulties with older mailers. It has
| been suggested that 66 character lines are the most readable.
| [...]
'-----
.-----<http://slrn.sourceforge.net/wishlist.html>
| [...]
|
| Support format=flowed
| Suggested 2004-08-05 by Martin Trautmann unscheduled
| slrn could support flowed text that can be wrapped according to
| preferences of the reader. This is specified in RFC 3676, but does not
| seem to be widely used on Usenet.
|
| [...]
'-----
> In opera.general Rijk van Geijtenbeek wrote:
>
>> Op Thu, 12 Oct 2006 20:22:39 +0200 schreef Whiskers
>> <catwh...@operamail.com>:
>>
>>> I'm not using Opera to read and post in newsgroups; I use slrn,
>>> one of
>>
>>> the fastest and most powerful tools for the job.
>>
>> A pity both GoldED and slrn don't support format=flowed :-)
>
> The point is that the poster should observe and post correctly for
> the medium. Only the poster can store a message on the server in
> line-breaks-at-72-characters (or whatever). Most News Readers on the
> other hand have local options to "wrap long lines". The onus is on
> the poster here and in all cases IMHO.
>
Not everyone is using 80 character screens. Many, if not most, are using
much longer lines than that.
Back in the days before the "world wide web" the internet standard was:
only send carrage returns at the end of each paragraph. It was the job of
the reading program to format the line length for each receiving terminal.
A lot of people had 40 character screens and some had only 16 character
screens.
All the news and email programs operated that way, some of those programs
are still in use today.
--
Opera 9.02.8585, java 1.5.0_07, win98lite, PII 400mhz, RAM 320meg, video
Intel740 pv4.0.
-[ ]-
> On Thu, 12 Oct 2006 15:25:48 -0500, Mark V
> <notv...@nul.invalid> wrote:
>
>> In opera.general Rijk van Geijtenbeek wrote:
>>
>>> Op Thu, 12 Oct 2006 20:22:39 +0200 schreef Whiskers
>>> <catwh...@operamail.com>:
>>>
>>>> I'm not using Opera to read and post in newsgroups; I use
>>>> slrn, one of
>>>
>>>> the fastest and most powerful tools for the job.
>>>
>>> A pity both GoldED and slrn don't support format=flowed :-)
>>
>> The point is that the poster should observe and post correctly
>> for the medium. Only the poster can store a message on the
>> server in line-breaks-at-72-characters (or whatever). Most
>> News Readers on the other hand have local options to "wrap long
>> lines". The onus is on the poster here and in all cases IMHO.
>>
>
> Not everyone is using 80 character screens. Many, if not most,
> are using much longer lines than that.
It is not about the screens or the newsreaders! The RFC written for
NNTP communication adopted similar at the time standards as e-mail.
Break lines at ?? characters.
This is about respecting the "rules" and readers of posts. Period.
[ ]
But I will not make a Federal Case of it. Only hoping to inform the
"offender" in this thread such that she is aware of the "why".
Clearly people will go their own way and do whatever they feel like
often enough and etiquette be hanged.
I must stop now and exit this thread before it degenerates into
arguments ad nauseam on this and such as HTML mail, etc.
Previously posted (Whiskers) were links to this topic. You (all) may
want to read them.
> I'm not using Opera to read and post in newsgroups; I use slrn,
> one of the fastest and most powerful tools for the job.
Ha! Welcome to the 20th Century!
--
Chris Game
"It's not a good idea to look too hard at the words, they
resent it." -- T. Pratchet, "Mort".
>> The bookmarks themselves are kept in a file called opera6.adr, which on
>> my system contains a line specifying utf8 encoding.
> ...this is very relevant.
> Here must be the problem.
> I've "UTF-8" too but may be it wasn't so in previous versions.
All versions from Opera 6 and onwards should store the bookmarks file in
UTF-8 encoding. Did you open the file in a text editor that changed the
encoding so that Opera was confused when reading it back? Does adding new
bookmarks with characters >=128 work as expected?
Whiskers <catwh...@operamail.com> wrote:
I can do exactly what I want to; I can set the DisplayMargin du 78 and the QuoteMargin to 65. That's what was recommended in 1990... :-)
But that means that reader cannot use his "FitToWidth" function any more, as there are a lot of CarryReturn, and messages are very long; they'll request several PageDwn and this is *very* boring for people. And people were complainting against me for that, because that lot of CR's made a garbage on their screen as they were using bigger televisions and variable Fonts.
I'm not saying you are wrong.
I just say I had to make some choices, and the actual one is to not stamp any CR as EndOfLine, letting the reader wrap my paragraphs himself.
"Rijk van Geijtenbeek" <ri...@opera.removethiz.com> wrote:
>> I'm not using Opera to read and post in newsgroups; I use slrn, one of
>> the fastest and most powerful tools for the job.
> A pity both GoldED and slrn don't support format=flowed :-)
All problems with Golded and may be (if any) with Opera, can now be solved by the use of MIMEProxy from Philippe Lamaizière.
May be I can explain how it works, as this is (at my knowledge) the *only solution* in the World for all Charset, UUCode and base64 encoded messages:
I'm using WindowsXP.
-Ensure that "localhost 127.0.0.1" is reachable in your FireWall, both directions.
-Install MIMEProxy listening on some Ports you define yourself, depending what kind of mail you are planing to translate. On my system, MIMEProxy listens to port 6000, 6001 and 10000.
-Tell your mailer (that sends/get the mail/news to/from your Provider) that for sending Mail, it must deal with "localhost 6000"; for getting Mail "localhost 6001"; and for get/send News "localhost 10000".
-Tell MIMEProxy that whenever something commes through Port 6000, it calls the Provider on Port25; through Port 6001, on Port110; through Port 10000, on Port119.
MIMEProxy will convert both directions your mail, from/to the Charset you choose. Including UTF-8. Including QuotedPrintable. Including UUCode or base64 encoded text.
It uses ICONV.DLL (normally already present on your system).
The version I use is firmly into the 21st century; where have you been?
So your program allows the display that you set (presumably to suit your
own equipment and preferences), influence what your articles look like to
everyone else? That's bad design, in my opinion.
> But that means that reader cannot use his "FitToWidth" function any
> more, as there are a lot of CarryReturn, and messages are very long;
> they'll request several PageDwn and this is *very* boring for people. And
> people were complainting against me for that, because that lot of CR's made
> a garbage on their screen as they were using bigger televisions and
> variable Fonts.
Presumably those people are not using usenet newsgroups; I've never seen
anyone complaining 'the lines are too short' (except in one memorable
instance where someone was using a web forum interface to a newsgroup and
putting a CR and LF at the end of every line to make the text fit into the
width of a rather small 'text box' the interface gave them - they were
only getting about five words to a line).
Reading long lines is horrible, even if they do fit within the display -
that is why scribes invented 'columns' and 'pages' about 3,000 years ago.
Scrolling down is trivial on any computer display, but scrolling sideways
is sometimes not even possible.
> I'm not saying you are wrong.
> I just say I had to make some choices, and the actual one is to not
> stamp any CR as EndOfLine, letting the reader wrap my paragraphs himself.
Then perhaps you (and they) should use genuine 'format=flowed', which would
probably mean you would have to start using one of the few programs that
can send it - eg Opera. Genuine 'format=flowed' is designed to allow
'fixed line length' programs to display and 'quote' correctly.
Format=flowed was actually invented to try and make email more legible on
the displays of small hand-held devices such as mobile phones - ie the
'very narrow display' problem, not the 'very wide window' reader preference
that you seem to be trying to cater for, but it will do that too as it
happens (as long as the people who wwnt to have very long lines across
their wide windows, also use a program that can recognise format=flowed).
<http://joeclark.org/ffaq.html>
What you are 'sending' at the moment are infinitely long lines, which is
just plain wrong. People get tired of having to re-format illegible
articles such as yours, if they can be bothered to read them at all.
No, they can't.
I'm not using Opera to read newsgroups, but I suspect that Opera can cope
with your infinite line length quite well, at least for reading. Such
things can be found on web pages, which are what Opera is built to
display.
> May be I can explain how it works, as this is (at my knowledge) the *only solution* in the World for all Charset, UUCode and base64 encoded messages:
It's a way of handling uuencoded and Base64 emails if your email program
lacks the functionality itself. Not the only way. But you aren't sending
your newsgroup articles in Base64 or uuencoded.
> I'm using WindowsXP.
We all make mistakes.
> -Ensure that "localhost 127.0.0.1" is reachable in your FireWall, both directions.
> -Install MIMEProxy listening on some Ports you define yourself, depending what kind of mail you are planing to translate. On my system, MIMEProxy listens to port 6000, 6001 and 10000.
> -Tell your mailer (that sends/get the mail/news to/from your Provider) that for sending Mail, it must deal with "localhost 6000"; for getting Mail "localhost 6001"; and for get/send News "localhost 10000".
That line is 211 characters wide.
Newsgroups are not email and email is not newsgroups.
> -Tell MIMEProxy that whenever something commes through Port 6000, it calls the Provider on Port25; through Port 6001, on Port110; through Port 10000, on Port119.
>
> MIMEProxy will convert both directions your mail, from/to the Charset you choose. Including UTF-8. Including QuotedPrintable. Including UUCode or base64 encoded text.
> It uses ICONV.DLL (normally already present on your system).
All of which has nothing to do with your infinitely-long lines. But why
should anyone use a special program just to read your articles? Get real!