The letter ç (portuguese)

error happens when importing articles in Portuguese containing the letter
ç. Appears \ cc instead of ç
  • that's not a general problem. Zotero will correctly import any utf-8 character (which includes ç) from a correctly encoded file. Where are you importing from?
  • works fine on mendeley. i`m importing from PDF metadata. (PDFS downloaded from SCIELO.ORG)
  • Zotero has a scielo.org translator that should work nicely - that would be the best way to go rather than using retrieve metadata from the PDF, which is always a 2nd best.

    Zotero and Mendeley use different strategies to get Metadata for PDFs (neither actually reads the metadata from the PDF, both try to look it up online), so you'll see different results.

    If you have a link to the scielo source we can take a look, but it's not very likely we'd be able to change anything.
  • Thanks! Worked Well.
  • Similar problem when importing using zotero plug-in in google chrome.

    When I try to export(using zotero desktop) to .bib file, ç appears as {\textbackslash}cc in the resulting file. Tha same in word2007 zotero plug-in
  • That's not the case with with a correctly entered ç - if you just copy the letter from your post above into a Zotero item it will, depending on the charset settings, either export as ç (utf-8) or as {\c c} (iso-8859-1)

    are you entering the ç using tex escaping? That would give you the escaped backslash.
  • If this is about import we need to know how it looks in Zotero and where the import comes from. As I say above, Zotero correctly imports this when it's presented correctly.
  • I am trying to import from scholar.google.com using zotero plug-in. I have tried with both, mozilla and chrome plug-ing. And with both plug-ins the ç is imported to zotero as \cc. I think it has to do with scholar.google.com because in other sites like scielo.br it works fine.
  • which item specifically are you importing?
  • Any search in scholar.google.com.br that has as word with ç

    For instance:
    http://scholar.google.com.br/scholar?hl=pt-BR&q=situa%C3%A7%C3%B5es&btnG=&lr=

    Then I click the zotero plug-in icon and choose any of the itens that shows in the window "zotero item selector". Then it appears in the right botton side a window showing the name of the item being saved. The name of the item in this window appears with \cc instead of ç as in the zotero desktop after.
  • The workaround I found is to export everything in zotero desktop to a .bib file and then using a texteditor to replace any entry that has {\textbackslash}cc to ç then I save the file and import it back to Zotero.

    It is not a big deal and I think it is much better then the limitations I was having with Mendeley.
  • Google Scholar exports the ç as {\c{c}}, which Zotero doesn't import correctly. We have plans to improve proper BibTeX parsing, but I'm not sure when this will actually happen.

    You should see the ç imported into Zotero as \cc, which you can fix. This will then export correctly.
  • edited September 13, 2013
    Ok thanks for the reply.

    A better workaround was to set google schoolar default import link to Refman and configure chrome to automatically open .ris file. As these files are exported in UTF8 Zotero had no problem recognizing the ç.

    Each entry in google schollar now has an import to Refman link, that when clicked redirects to Zotero.
  • That's essentially what Zotero does when you click the URL bar icon, except that it sets it to BibTeX instead of RIS. I think we chose BibTeX, because it was more complete.
  • @aurimas - IIRC, this one is the most difficult issue in fixing up bibtex, isn't it? Couldn't we fix this in a semi-general way (something like remove the inner parentheses when we have \{.+\{[a-z]\}\} ), implement some of the other stuff and make a lot of people happier?
  • I'll give bibtex translator another go this weekend. Hopefully we'll have this sorted out.
  • this now works correctly.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.