Comment 1 by briang1 on 2011-02-09 19:59
Hi, well most people are having no issues, so we need to find out what is unique in your installation. So, some questions.
Is this a clean install, ie have you been using a portable version and this is also a portable version and you simply unzipped it into the same folder?
If yes, then try it in a new folder and run it there. If its an installed copy, was there a working earlier version installed. It might be wise to reinstall it and see if it works.
Are you sure its a Windows error you are hearing and not the nvda error sound.

It would be nice to be able to see the log file, so if you have another screenreader maybe you could let us see the log? Details on this are in the documentation.
Lastly from me, what language and synths are set in the versionyou are overwriting, asuming you are of course.
If you were using an odd synth, the new version might not work any more as synths need their drivers updating if they are other than espeak or sapi ones.

I would have thought that it would default to espeak though.

Comment 2 by norrumar (in reply to comment 1) on 2011-02-09 20:35
Replying to briang1:
I have tried to run a portable version, and I have installed NVDA later, because I coud'nt run the portable version. But the installed NVDA doesn't work. None of those versions works. The sound is played by Windows; I have listened NVDA sounds, contained in Waves folder. I can't read the log file, because NVDA doesn't work. I have tried to run portable version using trhee machines, and the program can't be executed. I think that language is not producing that error, but those computers are configured in spanish. And I have changed my computer language now, but I can't start NVDA.

Hi, well most people are having no issues, so we need to find out what is unique in your installation. So, some questions.

Is this a clean install, ie have you been using a portable version and this is also a portable version and you simply unzipped it into the same folder?

If yes, then try it in a new folder and run it there. If its an installed copy, was there a working earlier version installed. It might be wise to reinstall it and see if it works.

Are you sure its a Windows error you are hearing and not the nvda error sound.

It would be nice to be able to see the log file, so if you have another screenreader maybe you could let us see the log? Details on this are in the documentation.

Lastly from me, what language and synths are set in the versionyou are overwriting, asuming you are of course.

If you were using an odd synth, the new version might not work any more as synths need their drivers updating if they are other than espeak or sapi ones.

I would have thought that it would default to espeak though.

Comment 3 by jteh on 2011-02-09 21:21
Unfortunately, we cannot even begin to diagnose this without a log file. I'm assuming you have another screen reader or similar if you are able to write here. If not, you could use Narrator. The log file can be found quickly by doing the following:

1. Press Windows key+r to open the Run dialog.
2. Type: %temp%\nvda.log
3. This should open in Notepad. Now save this file somewhere you can find it and attach to this ticket.
   Thanks.

Attachment nvda.log added by norrumar on 2011-02-09 21:32
Description:
Log file

Comment 4 by jteh on 2011-02-10 23:29
This is a bug in the Spanish localisation. The issue is that the {...} format specifiers (which are actually identifiers) have been translated when they should have been left as is.
Changes:
Milestone changed from None to 2011.1

Comment 5 by jteh on 2011-02-10 23:52
Also affected Galician.

Fixed in e120879.
Changes:
State: closed

Comment 6 by jteh on 2011-02-11 00:07
Peter: It'd probably be good to email and let the translator know that {...} format specifiers shouldn't be translated. I'm happy to send this email if you like, although you're also welcome to do so. If you want me to send it, is Juan C. buno the current translator?

This also raises another point: we probably need to test NVDA startup with all new translations to catch bugs like this. We can't really do any error handling for this, as there's no way to recover even if we catch the error.

Comment 7 by jteh on 2011-02-11 00:09
Changes:
Changed title from "I can't start NVDA" to "NVDA fails to start with Spanish and Galician translations"