export naming

Marco M. Jaeger

• 2018年08月02日 23:05

Hello
I got to process receipts selected and I'd like to use image name as the output naming - however for the 2nd check process recipe I'd like to e.g. add the dimensions to the file name - I tried to put it into Sub Name but whatever I try just doesn't work - could anybody please tell me how to do this.

Thanks

0

• 

  Eric Valk

  • 2018年08月03日 03:30

  In the export naming field, you can add a token called "Dimensions" by dragging it from the list of tokens into the name field. The dimensions of the image become part of the name of the exported file.

  0
• 

  Marco M. Jaeger

  • 2018年08月03日 11:52

  I saw that but it affects both process recipes - do I need to process the first recipe and then the 2nd recipe and add the dimension token to the 2nd recipe beforehand.

  0
• 

  Eric Valk

  • 2018年08月03日 13:16

  It's not very obvious in the CO GUI, but you can define User Presets for naming, and you can select presets for naming.
  
  You could define one naming preset for the first recipe, and another for the second recipe, but if so, you will still have to manually select the naming preset to match the recipe.
  
  Alterntively, you scan set up both naming and processing with AppleScript.

  0
• 

  SFA

  • 2018年08月03日 18:49

  Have you tried putting the Dimensions token in the Sub Name Field and then the Sub Name token in the file naming Format?
  
  
  Grant

  0
• 

  Marco M. Jaeger

  • 2018年08月03日 21:12

  [quote="SFA" wrote:
  Have you tried putting the Dimensions token in the Sub Name Field and then the Sub Name token in the file naming Format?
  
  
  Grant

  
  
  Thanks Grant - that seems to work although a blank at the beginning gets ignored.

  0
• 

  SFA

  • 2018年08月04日 10:40

  [quote="mmjaeger" wrote:
  

  [quote="SFA" wrote:
  Have you tried putting the Dimensions token in the Sub Name Field and then the Sub Name token in the file naming Format?
  
  
  Grant

  
  
  Thanks Grant - that seems to work although a blank at the beginning gets ignored.

  
  
  In general, in my opinion across all types of computer usage, a blank at the beginning of something is best avoided or ignored if not avoided, however in your context can you explain a little more about where this blank comes from?
  
  
  Grant

  0
• 

  Marco M. Jaeger

  • 2018年08月04日 12:08

  [quote="SFA" wrote:
  

  [quote="mmjaeger" wrote:
  

  [quote="SFA" wrote:
  Have you tried putting the Dimensions token in the Sub Name Field and then the Sub Name token in the file naming Format?
  
  
  Grant

  
  
  Thanks Grant - that seems to work although a blank at the beginning gets ignored.

  
  
  In general, in my opinion across all types of computer usage, a blank at the beginning of something is best avoided or ignored if not avoided, however in your context can you explain a little more about where this blank comes from?
  
  
  Grant

  
  
  I've got token imagename - dimensions - so I'd like to add a blank before and after the dash

  0
• 

  SFA

  • 2018年08月04日 13:21

  [quote="mmjaeger" wrote:
  

  [quote="SFA" wrote:
  

  [quote="mmjaeger" wrote:
  SFA wrote:
  Have you tried putting the Dimensions token in the Sub Name Field and then the Sub Name token in the file naming Format?
  Grant
  ==========================================
  
  Thanks Grant - that seems to work although a blank at the beginning gets ignored.

  
  
  In general, in my opinion across all types of computer usage, a blank at the beginning of something is best avoided or ignored if not avoided, however in your context can you explain a little more about where this blank comes from?
  
  

  
  
  I've got token imagename - dimensions - so I'd like to add a blank before and after the dash

  
  
  Type it in to the format line between the tokens with the dash in the middle.
  
  I think spaces are OK for folder names although I prefer underscores since at least you have something visible to work with. It's not always easy to know whether a space is a single space or two spaces and not knowing can, in many circumstances connected with data processing, be extremely inconvenient.
  
  For file names, where sorting can be affected by the same challenge, I just don't see it as a good idea.
  
  Moreover whilst these days we are rarely constrained to the filenames of an 88888888.333 format as was once the case it is still helpful to make the name as compact as possible for display purposes (for humans) and as good practise when dealing with databases and their internal file structures. Really in your format the dash (or in may case underscore) should be adequate and easier to apply consistently and visibly than spaces. They might be considered to make the name look prettier but the computer doesn't care about that and realistically hardly anyone else will either.
  
  Choose the wrong font for output and it can be very difficult with some character combinations to know whether or not there is a space (or two) between characters anyway, as mentioned earlier.
  
  HTH.
  
  Grant

  0

投稿コメントは受け付けていません。