# Nunavut universal character name error

**URL:** <https://forum.opencyphal.org/t/nunavut-universal-character-name-error/1361>\
**Category:** Nunavut\
**Created:** [July 21, 2021, 11:28am UTC](https://forum.opencyphal.org/t/nunavut-universal-character-name-error/1361 "2021-07-21T11:28:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![q.twisk](https://forum.opencyphal.org/letter_avatar_proxy/v4/letter/q/8dc957/32.png) [@q.twisk](https://forum.opencyphal.org/u/q.twisk)\
**Post date:** [July 21, 2021, 11:28am UTC](https://forum.opencyphal.org/t/nunavut-universal-character-name-error/1361/1 "2021-07-21T11:28:19Z")

</div>

I am currently working with the auto generated headers using Nunavut on Windows. It generates code with the following assert:

```auto
static_assert( NUNAVUT_SUPPORT_LANGUAGE_OPTION_TARGET_ENDIANNESS == 434322821,
              "C:\Users\xxx\xxx\xxx\xxx\Position.1.0.uavcan is trying to use a serialization library that was compiled with "
              "different language options. This is dangerous and therefore not allowed." );

```

This raises the error:

```auto
error: incomplete universal character name \U

```

This is because of the C:\Users part in the assert error message. Is there any way to solve this in Nunavut so that I dont have to manually remove these parts?

---

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [July 21, 2021, 11:31am UTC](https://forum.opencyphal.org/t/nunavut-universal-character-name-error/1361/2 "2021-07-21T11:31:24Z")

</div>

This is a known issue on Windows:

> <https://github.com/UAVCAN/nunavut/issues/195>
>
> Problem description
> When generating C headers on Windows with, the DSDL source file paths are generated incorrectly, causing compile-time warnings, e.g: warning:...

I think it should be trivial to fix, just replace a few calls to pathlib around the codebase. Can you look into it?