Oolite Bulletins

That's it! My Vista discs won't install to a VM, since they're tied to the laptop hardware itself.. so I can't use them now I've switched the laptop to Mint.

Re: turning off Windows' hide file extensions

That's the first thing I do when I start using a Windows PC at home or work.

Thanks commanders,

Anyway, Notepad++ seems to work great and I am on the job now.
I will probably need some help of computing skills on the end, just as like 2 years ago for previous version...

Poovga

Hello Commanders,

All the files are translated, edited with Notepad++
I copied the FR files in Config, then started with the shift key.
Well, the log says is rebuilding cache but stops with the following line:

15:52:37.541 [plist.parse.failed]: Failed to parse Resources/Config/descriptions.plist as a property list.
Parse failed at line 1 (char 1) - extra data after parsed string

I tried to copy the first line from the original English version with no result.
Any clue?

Thanks guys

If you are using the current 'openstep' code, the first line should simply consist of an open curly bracket like this '{' as in the core game's descriptions.plist - see below which is the first five lines (most of which are comments on the code).. If you are using the old XML code, the header should look like this

Smivs wrote:

If you are using the current 'openstep' code, the first line should simply consist of an open curly bracket like this '{' as in the core game's descriptions.plist - see below which is the first five lines (most of which are comments on the code)..

Code: Select all

{

It's exactly what I see and what I copied from English...
I go on trying... A strong will to counterbalance weak skills

Thanks

The 'real' problem may lie further into the code a line or two further down. If you c&p the whole plist here (between 'code' tags) we can all have a look and somebody may find the problem.
These things can be frustrating, but they are fixable

These are the first lines of description.plist


{
// Plural-form handling.

// * The format is an array of rules, each one a string, as set out below.

// * |index| is, by default, 0 for the first rule.

// It is incremented by 1 for each following rule.

Anything strange?

Thanks

That certainly looks OK. Had you previously been editing this plist with notepad? as it could still contain hidden extra characters if that is the case.
Maybe try re-building it - start a new document and begin with the curly bracket, then c&p the rest of the plist (without line 1) into your new document, and save it. Maybe even manually add the last line as well, just in case.

If you are using Notepad++, look at the bottom right of the window. Does it say UTF-8 as in the screenshot below (click to view full size)?

If yes, go to Encoding menu and select "Encode in UTF-8 without BOM". Save and restart Oolite with Shift held down.

The c&p trick helped a lot
The log shown two lines I broke during translation: missing "(" and "/" - corrected!

Now the restart stops at the last character: "}"
By the way, it's blocking 53683 characters away from the previous post! It's a small victory!

17:23:41.794 [plist.parse.failed]: Failed to parse Resources/Config/descriptions.plist as a property list.
Parse failed at line 1545 (char 53683) - reached end of string

Here are the last lines -in case a character is missing somewhere:

// Mac multi-screen handling
"oolite-mac-bad-display" = "La configuration de l'affichage a changé d'une manière qui peut avoir un impact pour les performances d'Oolite.";
"oolite-mac-bad-display-2" = "La fenêtre principale d'Oolite est désormais sur un écran qui n'est pas connecté à un processeur graphique compatible avec Oolite. Oolite devrait pouvoir continuer à fonctionner mais avec des performances dégradées.";
}

I am encoding in UTF-8 without BOM - Good to check anyway

Sorry, I have to go now.
With your brains guiding my fingers, it's on the right track!

Thanks commanders

Getting there
Could you show us line 1545 where the parse failed or is that the last (curly bracket) line?
If so it might be worth deleting that line, saving, then re-inserting the bracket manually.

Often the parser gives unhelpful error messages. If it's complaining about something in line 1, most often the real reason is a missing (or extra) comma, colon, quotation mark, or bracket somewhere down the line. Thus you have no choice but to check the whole plist.

Bonjour !

Je ne trouve pas tatraduction dansles OXP, y est elle toujors ?

Merci pour ton travail.


Hi,
I can't find the oxp in the list, is it still here ?
thanks for your work