Jump to content

BloodDrop

Members
  • Posts

    20
  • Joined

  • Last visited

Recent Profile Visitors

546 profile views
  1. No,no, I mean the file structure should be included or an example file. This definition alone is not clear enough. It is easy to interpret it as the correct answer, if you already have the answer Notice, the basic json structure meets the requirement as well, yet is not right for this application. Anyway, it works and I hope others will find the answer here useful.
  2. Ok, that is interesting Thanks Walt, that does explain a lot. Apparently, we need an array ( [ ] ) in the first level, and then every "row" of our table is an object ( {} ) containing a field:value pair for each cell in the row. Yep, this should definitely be included in documentation for Publisher. Thanks again Walt, helpful as always
  3. These files are so simple, it does not require any complicated files to recreate the problem. The most basic json file should work, even if resulting in a lacking data structure. With CSV you can simply put some words, separate them with commas, and you can see how it is interpreted by Publisher. Then you can make adjustments. In the json case, I don't even know how it is understood by the application. I started with the simplest example: { "Name": "Test", "Mobile": "12345678", "mail": "atsomething" } I have tried making the whole thing an array using "[]" as the top level. I have tried changing the values into arrays. I have tried changing the names into an array. But nothing wanted to compile. I have even used a table-structure with the json syntax, knowing only the first level would be parsed. I agree with Old Bruce, it would be enough if we got a working json file as a reference, instead we are trying to wrap our heads around it and wasting time.
  4. This is simply infuriating! I have tried a lot of different JSON structures to get the data, but nothing works. I get the same error as TenTen71 or a "syntax" error, even though my file is fine. If there is some specific structure of a JSON file we should use, could we get the "recipe" in documentation for data merge? If it is not about structure, could someone confirm or deny that the problem exists?
  5. Oh, I do agree! I have just made my first "serious" table in Publisher and it was not an easy task. I hope it gets some more attention, although I recognize there are more pressing matters currently.
  6. Hi guys, I had the same problem - I tried the dictionary files taken from Libre Office but they did not work at all. The language was recognised by AP regardless of where I put them - whether the default location or the additional one you can set up in the preferences - but spell-check did not recognise any words. I found the solution in this thread: It is true that dictionary files from different sources may work differently for some reasons - wrong encoding, some additional content within the file, or even being saved from GitHub "the wrong way". I downloaded the .aff and .dic files from the unofficial website of the Dictionary of the Polish Language - https://sjp.pl/slownik/ort/ and they worked like a charm! Later I downloaded the Libre files one more time, making sure they contain only the required list of terms, and they work nicely too (while I guess the Libre one is more reliable, it hasn't been updated for several years, and the SJP dictionary is a bit bigger as it has been constantly developed by the fans). The issue of hyphenation not working can stem from the same problem. Make sure it is the right file with no additional stuff and saved in the proper encoding standard. It will work. You can always download the collection mentioned in the thread by Ixolite - https://github.com/LibreOffice/dictionaries/archive/master.zip
  7. Thanks Callum for the info. Unfortunately, the articles deal with the same info I have seen in multiple other websites and tutorials. I do know what CMYK is, and how it differs from RGB, and what Pantone means in this respect... I also know how to prepare material for printing. What I still don't know is why in Affinity the colour workflow gives me different results to those from other applications. Why RGB to CMYK / CMYK to RGB conversion gives the results I would not expect. What would be the right approach to creating a designer file containing a complete set of logo versions suitable for export to both web and printing purposes. The time when we had to create separate source files for print are long gone and most applications I know now rely on creation in RGB and conversion to the right colour range at the export stage. But Consistency is the absolute requirement in this case. What should we do to achieve this consistency in the Affinity package? Maybe the currently published videos will take up this topic at some point and they will answer all my problems I truly hope they do.
  8. Hi guys, some of you might see this as a silly question, but I have worked with Designer for a long time and I still get confused a lot when it goes to working with colour. Do you know of any workflow oriented tutorials? Or maybe we could come up with one. I would be happy to contribute if possible, but I would also need to get some answers myself... I do know the difference between RGB and CMYK, I know what colour profiles are, I know all the basic stuff most tutorials focus on. What I don't know is how these colour formats work in Designer and how they determine our work. For example, regardless of the colour format I choose for a document, I get the same set of colour tools and changing the format seems to result just in the way colours are displayed, which cannot be true. When I change from RGB to CMYK or greyscale I would expect to lose some data, but colours seem to keep all the values. Converting between RGB and CMYK gives different values than in other editors or online converters. When I choose black from the Greys palette, it gives a fine RGB black which in CMYK is totally inconsistent... It would be great if users, both the current and the future ones, had a tutorial showing a full workflow regarding colour management in several cases, such as logo creation and export to assure consistency, or verification of an existing document, e.g. checking if a corporate identity book is correct and in alignment with the used logo files. I would appreciate if anyone shared their experiences or had any comments, as I may be the only person in the world with such doubts
  9. I have huge hopes when it goes to indexing, and variables, and references. These functions are used extensively in DTP, yet InDesign has never bothered to deal with them correctly. I would love to see a simple way of marking text as a variable and later pasting it by means of an auto-updating field, or making an index of these variable marks, or self-numbering "works-cited" list, or a reusable template for many instances of one document, each instance differing in several parameters (e.g. a booklet for a particular person with the ability of changing the name once, and automatically filling out all fields with the name)... It would also be great if we had more control over the auto-generated index - a kind of an object, or a customizable form would be great in which we could define styles for the whole object instead of treating the whole text as "text"... Just like CSS and HTML... This would also be great with regard to building interactive PDF forms, or something... The beta is nice and brings hope to the people :) I can't wait for the full version after the first major update... just like with photo or designer 1.5 ;)
  10. I would not like to take your time, as this is a minor problem for me. I'm more interested in it out of curiosity, as it might happen in the future with some photos of much higher value :) It would be nice to know what to avoid while making pictures to get the best result in HDR... more so, when you realise that panorama in AP is capable of creating almost decent spherical panoramas :) good enough for 3d hdri lighting...
  11. I'm sorry, the link got cut somehow... Here is the full and working one sample.zip
  12. Hi, of course, I will be glad to do so :) sample.zip Photos taken by the same camera with the same settings used to come out pretty nice...
  13. Can I pay you for the 2.0 update already? :) And for Photo too :) You guys bring faith in humanity back :)
  14. Hi, finally the moment has come that I have to ask for your help. Untill now I have always managed not to take your time, but now I am simply stuck. I am trying to make an HDR using 3 perfectly aligned photos of different exposures... Ususally I have no problem in doing that but in this case the result is terribly "posterised". Below are the source photos, and two results - one with all merge options unchecked and one with all options checked (by options I mean "align" and "remove ghosts" etc.). Does anyone have any idea of what might be causing such behaviour?
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.