# Importing filepath-propertyvalue pairs

**URL:** https://community.mp3tag.de/t/importing-filepath-propertyvalue-pairs/10730
**Category:** Support
**Created:** [August 28, 2010, 9:55am UTC](https://community.mp3tag.de/t/importing-filepath-propertyvalue-pairs/10730 "2010-08-28T09:55:53Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [August 29, 2010, 7:45am UTC](https://community.mp3tag.de/t/importing-filepath-propertyvalue-pairs/10730/7 "2010-08-29T07:45:30Z")

</div>

> [@DetlevD](#):
>
> As you discovered, the format string rules are partly different from the scripting rules.

What we have is some format strings using different rules from others.

e.g. in **Convert Text file - Tag** and **Convert Filename - Tag** single quote means single quote, whereas in **Convert Tag - Filename** and e.g. **Action Format value** single quote means "Output raw text".

This fits with the fact that the first type doesn't allow scripting and the second does. So I guess this is not a bug after all. But both are lablled the same on the UI - you have to look in the Help to discover there are two different types.

This is confusing and error-prone. I think the UI labels should distinguish the two types e.g. "Format string (not scriptable):" and "Format string (scriptable):".

---

_[View the full topic](https://community.mp3tag.de/t/importing-filepath-propertyvalue-pairs/10730)._