On Jun 27, 2011, at 18:12, Maxwell, Adam R wrote:

> 
> On Jun 26, 2011, at 15:26, Adam M. Goldstein wrote:
> 
>> There is another similar issue I have encountered.
> 
> I don't think this is really a similar issue.  Violating the syntax of 
> TeX/BibTeX, at least as understood by BibDesk, is the problem Cyril was 
> running up against...
> 
>> Importing from the Library of Congress, characters not in ASCII form are 
>> sometimes brought in. Then the database cannot be saved. The error log 
>> usually will say what the problems are. If there is more than one, the 
>> process of fixing records goes on, as each new problem record is identified 
>> during the saving process.
> 
> Error log as in system log, or alert sheet?
> 
>> I wonder, is there any way to create an alert when non-ASCII characters are 
>> in a record, the alert coming up as the record is imported?
> 
> Since non-ASCII characters are perfectly valid in BibTeX, there's no way to 
> warn of them in advance; there's no problem until you try to save them to 
> disk in some encoding that only supports a limited character set.  Even then, 
> the character conversion mechanism should make that a rarity.  

...of course, only if you have enabled character (TeX) conversion.

Basically, I'd either save in UTF-8, or in ASCII with TeX conversion enabled. 
If you save in ASCII without TeX conversion, you're basically telling us to do 
strict character checking, which can be useful, and is exactly what you say 
you're getting.

> What characters are causing you problems?
> 
>> And to provide a little more feedback, for instance, giving the cite key of 
>> the problem record?
> 
> Has this been rewritten?  The alert I'm thinking of used to give the citekey 
> of the offending item.  Since you mention a log, I could be off base.  
> Regardless, though, the problem can't be detected until you try to save data 
> in a specific encoding.
> 

No, this hasn't been changed, the alert mentions the cite key of the offending 
item, at least when we know about that.

Christiaan

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to