• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

P: Invalid Characters in Preset Names: Preset Export does not react

People's Champ ,
Sep 12, 2011 Sep 12, 2011

Copy link to clipboard

Copied

LR 3.5RC, Win7 64-Bit:

If a preset name contains some (for windows filenames) invalid characters (i.e. "/", "< Test"
"Test ? Test"

Beat

Bug Fixed
TOPICS
Windows

Views

126

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Oct 30, 2014 Oct 30, 2014
According to the bug record internally, it was fixed in 4.x

Votes

Translate

Translate
7 Comments
LEGEND ,
Sep 12, 2011 Sep 12, 2011

Copy link to clipboard

Copied

UPDATE: This post withdrawn, since it was based on misunderstanding...

Votes

Translate

Translate

Report

Report
People's Champ ,
Sep 12, 2011 Sep 12, 2011

Copy link to clipboard

Copied

Big missunderstanding:

I'm not talking about export presets, but about exporting develop presets carrying names in LR containing characters which are not valid in NTFS filenames.

Beat

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 12, 2011 Sep 12, 2011

Copy link to clipboard

Copied

Oops - my mistake. I apologize for responding without having read more carefully.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 19, 2011 Sep 19, 2011

Copy link to clipboard

Copied

Thanks Beat, I've logged this as a bug.

Votes

Translate

Translate

Report

Report
People's Champ ,
Sep 19, 2011 Sep 19, 2011

Copy link to clipboard

Copied

Thanks, Becky 🙂

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 30, 2014 Oct 30, 2014

Copy link to clipboard

Copied

Fixed?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 30, 2014 Oct 30, 2014

Copy link to clipboard

Copied

LATEST
According to the bug record internally, it was fixed in 4.x

Votes

Translate

Translate

Report

Report