# Bug about JabRef BibTeX String resolving for OSX?

**URL:** <https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179>\
**Category:** Help\
**Created:** [January 27, 2022, 7:54pm UTC](https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179 "2022-01-27T19:54:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![0hsuanyin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/0hsuanyin/32/1244_2.png) [@0hsuanyin](https://discourse.jabref.org/u/0hsuanyin)\
**Post date:** [January 27, 2022, 7:54pm UTC](https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179/1 "2022-01-27T19:54:07Z")

</div>

Hi all,

I’ve updated the newest JabRef version for OSX. I found that there seems to be a new bug that when I add a bib string, called @string{string\_name= “IEEE”} for the “address” field for my bibitem, and save it, I always get {#string\_name#} like this. Does anyone know why, and how I resolve it? In the case of {#string\_name#}, there always is a LaTeX compile error. I didn’t get this bug in the previous version.

Cheers

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [January 27, 2022, 8:40pm UTC](https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179/2 "2022-01-27T20:40:38Z")

</div>

HI,

the logic for BibTeX string resolving has been inverted. [jabref/CHANGELOG.md at main · JabRef/jabref · GitHub](https://github.com/JabRef/jabref/blob/main/CHANGELOG.md#changed-1)

By default JabRef resolves BIbTeX strings only for the fields defined in the preferences. However, you can add the field address to the list of existing fields in the preferences. e,g, `address;`  
Fields are separated by a semicolon

 ![grafik](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/2/240eacfe4d7c4c8c8a671da45e2d0f076ef51676.png)

---

<div class="post-metadata">

**Author:** ![0hsuanyin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/0hsuanyin/32/1244_2.png) [@0hsuanyin](https://discourse.jabref.org/u/0hsuanyin)\
**Post date:** [January 27, 2022, 10:27pm UTC](https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179/3 "2022-01-27T22:27:29Z")

</div>

> [@Siedlerchr](#):
>
> address

Thanks for the tip! Problem solved!

---

<div class="post-metadata">

**Author:** ![koppor](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/koppor/32/5_2.png) [@koppor](https://discourse.jabref.org/u/koppor)\
**Post date:** [November 11, 2024, 7:12pm UTC](https://discourse.jabref.org/t/bug-about-jabref-bibtex-string-resolving-for-osx/3179/4 "2024-11-11T19:12:10Z")

</div>

The CHANGELOG entry is

We inverted the logic for resolving [BibTeX strings](https://docs.jabref.org/advanced/strings). This helps to keep `#` chars. By default String resolving is only activated for a couple of standard fields. The list of fields can be modified in the preferences. [#7010](https://github.com/JabRef/jabref/issues/7010), [#7012](https://github.com/JabRef/jabref/issues/7012), [#8303](https://github.com/JabRef/jabref/issues/8303).