You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by twynn92 on 2012-12-07 05:53
When I add the "preserve" field to custom punctuation changes manually in symbols-xx.dic (where xx is your language code), NVDA respects said said field after a restart. However, if I make any changes via the Symbols Pronunciation GUI (Preferences --> Punctuation/symbol pronunciation) the field then disappears completely, leaving me only with the identifier, replacement, and level fields.
Example is below. I've started a new punctuation pronunciation file, changing "." and "," so that the preservation is set to 'never', which was done for someone on the NVDA freelist. That file is named 'before.dic' in this ticket.
After restarting NVDA, I went to the Symbols Pronunciation GUI, changed nothing, activated the "OK" button, and restarted NVdA.
The preserve field is now gone which is evident in the file named 'after.dic'.
The text was updated successfully, but these errors were encountered:
Reported by twynn92 on 2012-12-07 05:53
When I add the "preserve" field to custom punctuation changes manually in symbols-xx.dic (where xx is your language code), NVDA respects said said field after a restart. However, if I make any changes via the Symbols Pronunciation GUI (Preferences --> Punctuation/symbol pronunciation) the field then disappears completely, leaving me only with the identifier, replacement, and level fields.
Example is below. I've started a new punctuation pronunciation file, changing "." and "," so that the preservation is set to 'never', which was done for someone on the NVDA freelist. That file is named 'before.dic' in this ticket.
After restarting NVDA, I went to the Symbols Pronunciation GUI, changed nothing, activated the "OK" button, and restarted NVdA.
The preserve field is now gone which is evident in the file named 'after.dic'.
The text was updated successfully, but these errors were encountered: