Accentuated characters in CEL, CELX

[Paul Saumane]

Good evening,
I am trying to insert accentuated characters in a print command. For that purpose I followed recommendations displayed in the French forum which is to use (if I understood properly) Unicode Standard Latin-1 supplement with the following syntax :
quote \\uxxxx unquote. In other word a eacute is code \\u00e9 in the text.
Using that syntax and code, the code is displayed on the screen with just on slash-back.

Is it possible to confirm that it is the proper manner to display accentuated characters in Celx Celestia 1.5.0 or is it a change in the syntax ?
I tried &, #, {, ', \, \\uxxxx; ^ @ = <> § ! without success

Thanks in advance
Paul

[Vincent]

Hi Paul,

For some reason, Unicode does't work in celx scripts, whereas it does in cel.
I've reported this issue recently. The best thing to do is to use UTF-8 encoding that will allow
you to directly type accentuated characters (?, ?, ?, ...) in the script:

> [English] viewtopic.php?f=2&t=7615&start=0&st=0&sk=t&sd=a
> [French] http://www.ikiru.ch/celestia/forum/view ... 2&start=32

[Paul Saumane]

Hello Vincent,

Thanks for the tip.
Just an additional question: which type of editor are you using i.e. note pad, word pad and how to specify UTF-8. In word pad, if I save under unicode I got an error ....?
Sorry to be so beotian !
Best regards
Paul

[Vincent]

Hello Vincent,

Thanks for the tip.
Just an additional question: which type of editor are you using i.e. note pad, word pad and how to specify UTF-8. In word pad, if I save under unicode I got an error ....?
Sorry to be so beotian !
Best regards
Paul

Paul,

You're welcome.

As precised in the two links above, I use Notepad2:
http://www.flos-freeware.ch/notepad2.html

[Paul Saumane]

Hi Vincent,
Sorry, but it seems I got a problem :
Using note pad (MS Windows XP PRO SP2) and saving under UTF-8, when trying to open the CELX, I got an error and a Celestia crash.
Using Writer of OpenOffice opened and Saved in UTF-8 same result
I was thinking of a CR LF problem but I don't think that Note pad is adding such a thing. If I do not touch anything in word pad then the file (it is not my own i'm just translating from English to French) is opened and saved in ANSI (I am not always familiar with the codes).
Regarding Wordpad I can just saved under rtf, text, ms-dos text and unicode ... unicode generates the same error.
Any clue ?
thanks
Paul

Hello Vincent,

Thanks for the tip.
Just an additional question: which type of editor are you using i.e. note pad, word pad and how to specify UTF-8. In word pad, if I save under unicode I got an error ....?
Sorry to be so beotian !
Best regards
Paul

Paul,

You're welcome.

As precised in the two links above, I use Notepad2:
http://www.flos-freeware.ch/notepad2.html

[Vincent]

Paul,

Notepad2 - which is far superior to the standard note pad - will do the trick, as precised above.

[Paul Saumane]

Hi Vincent,

Sorry but from time to time I have some difficulties with my IC (QI) and thanks again for the tip.
I'll try that .
Thanks
Paul

[Paul Saumane]

Paul,

Notepad2 - which is far superior to the standard note pad - will do the trick, as precised above.

Thanks Vincent, with Notepad2 and converting to UTF-8, it works without error.
However and as you know translation means generally longer text . To make it readable I have just to extend the duration. But it is not the only point, now some scenes are not displayed any more or are shortened cuting some scene ends (motor separation and burning in the atmosphere as an example). In the CEL documentation there is not (apparently) any relationship between a longer text and some scenes which are not appearing any more. In fact it seems that because of the text the scenario does not follow the proper timing and the module is still orbiting when it is supposed to have landed.
Have you already faced such problem ? is it a matter of long text or accentuated text ? Do you think that extending duration will solve the problem ?
It seems that I do not encounter that problem from French to English and with CEL script
Thanks in advance
Paul
for info but I do not think that it is a Hardware problem, My config :
ASUSP4C800Edeluxe, P4-3Ghz- 2GRAM - AGP8x -ATIHD3850-512DDR3-WXPPRO-SP2

[BobHegwood]

Just a related FYI...

Have been using Notepad2 for over a year now, with excellent results.Get it HERE.

Thanks, Bob

[Paul Saumane]

Just a related FYI...

Have been using Notepad2 for over a year now, with excellent results.Get it HERE.

Thanks, Bob

Thanks for the tip, I guess it is not a matter of Notepad2 (which I use now and appears very impressive) but probably a sentence length compared to English.
Then the question mark is to know if there is a relationship with scenario timing(s), I'll check this evening in increasing the print duration.

Thanks again

Paul

[Vincent]

However and as you know translation means generally longer text . To make it readable I have just to extend the duration. But it is not the only point, now some scenes are not displayed any more or are shortened cuting some scene ends (motor separation and burning in the atmosphere as an example). In the CEL documentation there is not (apparently) any relationship between a longer text and some scenes which are not appearing any more. In fact it seems that because of the text the scenario does not follow the proper timing and the module is still orbiting when it is supposed to have landed.
Have you already faced such problem ? is it a matter of long text or accentuated text ? Do you think that extending duration will solve the problem ?
It seems that I do not encounter that problem from French to English and with CEL script
Thanks in advance
Paul
for info but I do not think that it is a Hardware problem, My config :
ASUSP4C800Edeluxe, P4-3Ghz- 2GRAM - AGP8x -ATIHD3850-512DDR3-WXPPRO-SP2

Paul,

I've never heard about this kind of problem before. Could you provide an example so that I can
try to reproduce the issue on my system?

Sorry to ask that, but did you make sure to increase the duration of the wait() command too?

[Paul Saumane]

However and as you know translation means generally longer text . To make it readable I have just to extend the duration. But it is not the only point, now some scenes are not displayed any more or are shortened cuting some scene ends (motor separation and burning in the atmosphere as an example). In the CEL documentation there is not (apparently) any relationship between a longer text and some scenes which are not appearing any more. In fact it seems that because of the text the scenario does not follow the proper timing and the module is still orbiting when it is supposed to have landed.
Have you already faced such problem ? is it a matter of long text or accentuated text ? Do you think that extending duration will solve the problem ?
It seems that I do not encounter that problem from French to English and with CEL script
Thanks in advance
Paul
for info but I do not think that it is a Hardware problem, My config :
ASUSP4C800Edeluxe, P4-3Ghz- 2GRAM - AGP8x -ATIHD3850-512DDR3-WXPPRO-SP2

Paul,

I've never heard about this kind of problem before. Could you provide an example so that I can
try to reproduce the issue on my system?

Sorry to ask that, but did you make sure to increase the duration of the wait() command too?

For the time being, I did nothing neither on print duration nor wait. I am going to try something now to see the evolution.
May I send you the file on a private posting for your appraisal because celx attachment are not allowed

thanks and regards

Paul

[Paul Saumane]

Hi Vincent,

Sorry, I am not familiar with forum here is the zip file

rgds

Paul

[Paul Saumane]

Hi all,

I have the filling that something happened with my installation of buran add-on and buran add-on extras, because now whether I am in English or in French I am not running the extras, i.e., "the splashdown" and atmosphere re-entry and landing.
My feeling is that the problem is coming from either Celestia or Add-on and not necessarily from the Celx.
I reinstalled the complete add-ons plus extras and run celx English version with the same poor result.
So I am going to clear-up everything then (re)download the complete set, download Celestia 1.5.1 and look at the result and report to you.
Regards
Paul

[Paul Saumane]

Hi all,

I have the filling that something happened with my installation of buran add-on and buran add-on extras, because now whether I am in English or in French I am not running the extras, i.e., "the splashdown" and atmosphere re-entry and landing.
My feeling is that the problem is coming from either Celestia or Add-on and not necessarily from the Celx.
I reinstalled the complete add-ons plus extras and run celx English version with the same poor result.
So I am going to clear-up everything then (re)download the complete set, download Celestia 1.5.1 and look at the result and report to you.
Regards
Paul

Just final on this subject I guess :
Hi All,
1) I just want to confirm that Notepad2 as stated by Vincent is the perfect way to encode accentuated characters just by setting encoding to UTF-8 and typing the corresponding accentuated characters.
Other editors seems to introduce added data which are corrupting the file.

2) I confirm that the display problem is coming apparently from the Celx depending at which level it is started (valid for both English and French version :
- if you preload the scenes, then you have a very short presentation of the flight
- if you go directly to the flight [3] then it runs properly and you are able to run the detailed celx.
- Of course you can follow the complete flight which is lasting several hours. However running 10x or more is also another way.

3) It is out of subject but loading N1-Lune designed for 1.4.1 seems to generate an error at the end and crash celestia 1.5.1 (I never checked with 1.5.0. However the launching area is really fantastic.

I'll advise the Author about the subject.

Thanks again for your kind and efficient help about that matter and hope to meet you again

Best regards

Paul