![]() ![]() Has Bitbucket made any recent changes to how authentication works on HTTPS over the last week? If so, I haven't received any notification. * With the number of repositories we have defined, I'm guessing converting to SSH would be a monumental task. Reasons for Choosing MadCap Flare: Everyone said Flare did it all - more powerful, better features, better support, fewer bugs. * We're using our correct passwords - the ones we've successfully been using for the last 6 months. * We haven't changed any configuration on Bitbucket or Madcap Flare. Madcap Flare is correctly configured to the relevant HTTPS server on Bitbucket, which worked correctly up until 5 days ago. ![]() * No network or firewall changes have been made on our systems during the last two weeks. We're not having any network issues our end. * This issue is occurring for members of staff that are working remotely from home and locally in the office. * Repeating this process a number of times doesn't ameliorate the issue. ![]() Source Control: request failed with status code 403 : Could not authenticate When we enter the username and password we get the following error: MadCap Flare is an all-inclusive solution for technical writers and content developers. Since MadCap Software was founded in 2006, customer adoption has been driven by a combination of innovative, state-of-the-art products and best-in-class service and support. However, about five days ago we can no longer perform pull, push, clones, etc.Įvery time we perform a function, for example a push, Flare asks for our Bitbucket username and password. Our HTTPS Git source control has been working fine over the last 6 months. But I just cannot seem to find any solution to make MadCap elements NESTED WITHIN H1 ELEMENTS translatable.My team have over a 100 Madcap Flare repositories branched to Bitbucket. Therefore, what I need to edit correctly at some stage is the parser settings for HTML 5.Īnd this is exactly what is slowly driving me crazy: I can define settings for h1 elements (which are translatable to begin with) and I can define settings for MadCap elements (which are not part of the default parser settings but must be created specifically). Yes, I have managed to import the nested elements as tags, but unfortunately, this is not what I want to achieve since Trados doesn't offer any possibility to edit tags.Īnother problem here is that the MadCap parser settings are irrelevant in this specific case because the keywords are not found in the Flare-specific files but in the topic files, which are "regular" HTML 5, but with proprietary MadCap markups. I know that I may be a silly question, but ¿were you able to convert the nested elements to Studio inline tags? If so, ¿could you convert them to translatable using the MadCap parser settings? I am quite interested in your problem and the way it can be solved it. Thank you in advance for any input on this! ▲ Collapse Agreement unites industry’s global leaders in solutions for developing, delivering and managing content, building on strong adoption by mutual customers. ![]() I understand that I somehow need to define the "MadCap:keyword" and/or "MadCap:keyword term" element as an editable element in the HTML 5 settings but having tried various options, I am now pretty much at my wit's end. MadCap Software Acquires IXIASOFT to Add Enterprise-Class DITA CCMS to Product Offerings, Expand Support for Customers’ Content Strategies. My "success" so far has been to make them visible as tags in Studio's editor but not as translatable content. The keyword entries are contained within header entries, and while I can translate the header entry ("Schichtprotokoll anzeigen und bearbeiten" in the above example), the keywords remain uneditable.ĭuring my initial translation run, where I was not aware of those keywords, I omitted them altogether and now I am finding myself struggling with importing them so they can be edited and translated. When opening the files in EmEditor, it displays something like this: However, it turns out that I omitted the keyword entries in the topic HTML files since those seem to be protected by Flare's HTML structure. 22, 2023 (GLOBE NEWSWIRE) -, Inc. So, its a good idea to use the XML Editor to edit. I have translated a huge software manual project in SDL Trados Studio 2017, consisting of HTML and FLSNP files from MadCap Flare. Acrolinx for MadCap Flare and Contributor- Supported Content. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |