Project Schedules and Deadlines

Deadlines stated or accepted by Wordcrafts are based on several factors. These factors include constraints imposed by both internal and external factors and persons and have all been taken into account during the deadline agreement or offering process which itself represents the schedule of all workflows and milestones involved.
 
To avoid disputes about the schedule or deadlines, we would like to use this opportunity to describe the most relevant factors customers can directly and indirectly influence. As the typical localization workflow contains two to three reviews following the initial localization delivery, the waiting time between delivery and availability of a new build containing the last delivery significantly influences the project schedule.
 
Wordcrafts always take into account a 48 hours build creation time in normal project scheduling and reserves resources for this period of time ensuring an imminent continueation of the project. In case the build provision time takes longer and the period stated above, Wordcrafts cannot guarantee the imminent continueation of the project and reserves the right to postpone the project continueation for a reasonable time – typically from some days up to a week.
 
In order to avoid waiting times, customers are asked to either provision a new build within the period stated above or communicate expected longer build provisioning times on quote agreement.
 
Wordcrafts appreciate open and direct communication for all agreements needed to be found.

Schedule completion

Localiaztion and translation work is a very abstract working art – result s are not imminently visible in their final form - as it is in software development.
 
In order to deliver perfect quality, we need to be allowed to fully complete the localiaztion and translation workflows. Projects aborted or stopped in mid-workflow can still contain linguistic and UI errors and flaws – Wordcrafts will not accept liability for any errors of any kind when the projects was not fully completed by Wordcrafts.
 
As Wordcrafts reserve human resources for QA purposes during the localization workflow, these QA efforts have to be compensated for as stated on the project quote – regardless at which point of the workflow the project was aborted by the customer.

Text integrity

During the course of the localization workflow, the text integrity is crucial for us.
 
This means that we have to be sure that what we see in a review build reflects the exact same state as what we have delivered before. This may be irritating, but this is crucial for us to perform efficient QA work.
 
Imagine a development team where a developer commits changes to the source code without a commit message and you do not have a diff tool. Horrible, right?
 
As our work will be implemented in your product, there is no way for us to track changes – so please simply help us by not editing the localized files yourself during the localization project.

Projects with existing localizations

Projects implying working an existing applications require some extra tasks to be performed by both Wordcrafts and the customer.

As the developer knows the application best, the customer shall provide extensive information on the existing localization and the part of the app requiring a localization update.
 
Wordcrafts will read into the existing localization and offer the following options:
 
  • Consistency adaption
  • Consistency creation

Communicate with us

During the localization workflow, we will have questions about the app, about specific strings or UI behavior.
 
We need the answers to create localizations that fit and work best with your application. Usually, we send a batch of questions only once in a project stage in order to not disturb you too often. Nice, aren't we?
 
Wordcrafts appreciates quick replies as they allow us to continue or finish our work. Please reply within 24 hours or let us know in case you cannot communicate with us for a specific time. That would ne nice for us.
 
In case customers have questions, are unsure about why we did something or belive that we made a mistake, please do ask – don't assume.
Assumptions too often lead to misunderstandings.

What we need to know

If you are interested in a quote, we are happy to analyse the scope of your resources. To do this, we need your uncompiled English resources containing all xibs, .strings files and any additional text files such as html help files or credits rtf documents.

What you need to know

We do not want your complete Xcode project containing your source code. Nevertheless if you feel your resources might need that extra protection, we are happy to sign a Non-Disclosure-Agreement.

DROP US A LINE

Drop us a line via Email
 
 
 
Back to Top